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

Tobias Deiminger bugzilla_noreply at kde.org
Sun Jan 26 23:48:55 GMT 2020


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

Tobias Deiminger <haxtibal at posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |haxtibal at posteo.de

--- Comment #17 from Tobias Deiminger <haxtibal at posteo.de> ---
(In reply to Postix from comment #10)
> There are also a few lines with
> > generatePixmap

Qt has a shortcut for QTimer::singleShot(msec = 0, ...), where they call
QMetaObject::invokeMethodImpl to trigger your lambda immediately via a
QueuedConnection plus one iteration through the event loop.

So a callstack like yours
#n+1 QMetaObject::invokeMethodImpl
#n   Okular::Generator::generatePixmap
...
#n-m QCoreApplicationPrivate::sendPostedEvents
could indeed stem from a "text generation already finished but mTextPageReady
still false" endless loop, assuming the compiler has inlined some calls for
optimization. Note the "could", I see no definite proof yet.

I generally agree with Albert that this issue is particularly hard to debug
without being able to reproduce it locally.

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


More information about the Okular-devel mailing list