-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disassembler performance is bad -> libQt5Gui #505
Labels
Comments
Merged
Related: #522 |
Just wanted to congratulate you on the performance adjustments - using most current appimage the "time to disassembly" is heavily reduced and finally also useable for huge functions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If using the disassembly function on a huge function, then hotspot stays at 100% cpu, which can (for huge functions) stay that way over an hour.
To Reproduce
open disassembly from huge program
Expected behavior
If it is too huge, possibly allow to use disassembly for a range of code lines.
Version Info (please complete the following information):
Additional context
pref recording for 30 seconds on the hotspot process, showing
perf.data.hotspot_disas.perfparser
Checking its stack by polling shows:
and "always" stays over the 0x00007f3b7aa815b7 frame (I can "finish" until I get there, but "finish" from there seems not not exit (waited for some minutes).
Not sure if details in libQt5Gui would help, but those are not contained in the debuginfo and https://github.com/KDAB/hotspot/blob/master/HACKING.md#debugging-the-appimage has no details on that either.
The text was updated successfully, but these errors were encountered: