Binary Ninja hangs for 10+ seconds when running command !process 0 0 in kernel debugging

[xusheng6]

In Windows kernel debugging, when I run the command !process 0 0 , the Binary Ninja UI will appear to hang for ten or more seconds, then all output lines will be dumped to the debugger console. However, if I run this in the WinDbg UI, lines will be dumped one-by-one, and its main UI does not hang. Though the overall processing time is similar (this command takes a long while to finish)

This is NOT a simple main thread congestion. There is something different in the threading model of binja's use of dbgeng and dbgeng's own assumption/expectations. Though I am not quite sure what is happening

[xusheng6]

Related to #591, the hang is because the command is executed on the main thread and it blocks until all of the output is dumped