Ok, Finally figured out the bug where for some captures, some protocol analyzers would not produce terminal output.
The problem affects MacOS (and probably Linux, will test soon). Basically the front end does not get any terminal data if the back end writes too many bytes to the terminal’s named pipe at once. Not sure why, but it appears to be a problem with the front end named pipe support, because reading works fine from the terminal.
Looks like we have a working fix and it should be in the next release.