Constant GARBLE message processing appearing in the recipient log
During a file transfer, the message concerning an out-of-order file part appears but never stops and seems to be stuck in a recursive loop (as far as the log displays).
Reproduction Steps
- Begin file transfer to recipient ID
- Witness debug log as transfer progresses
- Wait for file to have fully arrived and continue to watch log
Expected Outcome
Any GARBLE message events should attempt to be resolved or discarded, especially if a successful transfer has occurred.
Actual Outcome
GARBLE messages appear in the log file after the file transfer completes every 20-30ms as if stuck in a recursive loop. CPU time of the process appears to rise in line with this behaviour. See attached log.
Edited by Doxxier Dev Team