thank you for preparing this detailed bug report! Sadly, I have not been able to reproduce the hang so far. The backtraces are sadly often not helpful as they just contain a lot of generic Qt event processing functions. But since you are able to use gdb, would you be willing to dig into this further and using e.g. "perf top -p $(pidof qpdfview)" [1] to collect a profile during such a hang? This might help us to better isolate which part of the code base is hogging the CPU.
Hello Mark,
thank you for preparing this detailed bug report! Sadly, I have not been able to reproduce the hang so far. The backtraces are sadly often not helpful as they just contain a lot of generic Qt event processing functions. But since you are able to use gdb, would you be willing to dig into this further and using e.g. "perf top -p $(pidof qpdfview)" [1] to collect a profile during such a hang? This might help us to better isolate which part of the code base is hogging the CPU.
Best regards,
Adam
[1] https:/ /jvns.ca/ blog/2016/ 02/24/perf- top-my- new-best- friend/