[okular] [Bug 403643] Okular stops rendering PDF and uses up 100% cpu (possible regression)

[Postix]

https://bugs.kde.org/show_bug.cgi?id=403643

--- Comment #7 from Postix <postix at posteo.eu> ---
Created attachment 125427
  --> https://bugs.kde.org/attachment.cgi?id=125427&action=edit
gdb stacktrace

(In reply to Albert Astals Cid from comment #6)
> "thread apply all bt" in gdb
> Also ideally do that before closing


I tried it again, this time with a debug build of Okular and the qt-debug
packages on Manjaro Unstable in a virtual machine. Also glibc-debug was
installed, but it still seems to lack the debug symbols.

What did I do?

1) Started Okular with gdb
gdb okular
gdb run

2) Loaded a troublesome PDF and started scrolling until the CPU went high and
no more - not yet rendered - pages were loaded
3) Interrupted the process in the terminal by ctrl+c
4) Generated the backtrace via
thread apply all bt full

which is now attached and hopefully more useful to you now. If not, please tell
what I should do instead or additionally of steps 1) to 4). :)

> Also if you have a file in which it's relatively easy to reproduce, attach it
With 17 MB it's too big to attach it here. Maybe I can send it to you via mail?

-- 
You are receiving this mail because:
You are the assignee for the bug.