What happens here is that after the deferlow, trace highlights the cables of chain 1 (the chain connected to the deferlow), where i’d expect it to go to chain 2 first. Striking is that it doesn’t print the accompanying messages until chain 1 is terminated at the print. At that moment it prints all pending trace messages at once, then prints ‘Finished trace’, then starts working normally on chain 2.
I don’t think this is really a bug. I looks like printing of the trace texts is in the same queue as max events and gets deferred too? Something like that? I can’t really get my head around it yet..