Bug 326055 - Okular crashed while searching and reloading a file
Summary: Okular crashed while searching and reloading a file
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.16.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-10-15 15:53 UTC by Moritz Ulmer
Modified: 2017-03-28 22:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Ulmer 2013-10-15 15:53:34 UTC
Application: okular (0.16.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.8.0-31-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
The PDF document is repeatedly compiled from a latex source. This is done automatically with a rake script that detects when the source files change. Okular then automatically reloads the new PDF document. Sometimes while searching through the document, it crashes. This is a corner case crash as it takes several tries to recreated (~5) it.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe50e97d7c0 (LWP 890))]

Thread 2 (Thread 0x7fe4f821d700 (LWP 895)):
#0  0x00007fe50b9a73cd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fe5085e91dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe5085e9304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe50c3a7036 in QEventDispatcherGlib::processEvents (this=0x7fe4f0017be0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fe50c37738f in QEventLoop::processEvents (this=this@entry=0x7fe4f821cd90, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe50c377618 in QEventLoop::exec (this=this@entry=0x7fe4f821cd90, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fe50c279410 in QThread::exec (this=this@entry=0x11ea600) at thread/qthread.cpp:542
#7  0x00007fe50c358edf in QInotifyFileSystemWatcherEngine::run (this=0x11ea600) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007fe50c27bbec in QThreadPrivate::start (arg=0x11ea600) at thread/qthread_unix.cpp:338
#9  0x00007fe508abbf8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fe50b9b3e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7fe50e97d7c0 (LWP 890)):
[KCrash Handler]
#5  Okular::Page::hasTextPage (this=this@entry=0x0) at ../core/page.cpp:244
#6  0x00007fe4fcea3554 in Okular::DocumentPrivate::doContinueDirectionMatchSearch (this=0x9ba5f0, doContinueDirectionMatchSearchStruct=0x111b510) at ../core/document.cpp:1398
#7  0x00007fe50c3925be in QObject::event (this=0x99bf00, e=<optimized out>) at kernel/qobject.cpp:1194
#8  0x00007fe50cd628ec in QApplicationPrivate::notify_helper (this=this@entry=0x7b1090, receiver=receiver@entry=0x99bf00, e=e@entry=0x20575d0) at kernel/qapplication.cpp:4567
#9  0x00007fe50cd6525b in QApplication::notify (this=0x7fffb651ab80, receiver=0x99bf00, e=0x20575d0) at kernel/qapplication.cpp:4428
#10 0x00007fe50da6e1a6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#11 0x00007fe50c37863e in QCoreApplication::notifyInternal (this=0x7fffb651ab80, receiver=receiver@entry=0x99bf00, event=event@entry=0x20575d0) at kernel/qcoreapplication.cpp:946
#12 0x00007fe50c37c171 in sendEvent (event=0x20575d0, receiver=0x99bf00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#13 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x778670) at kernel/qcoreapplication.cpp:1570
#14 0x00007fe50c37c4a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#15 0x00007fe50c3a6e83 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#16 postEventSourceDispatch (s=0x7a8cf0) at kernel/qeventdispatcher_glib.cpp:279
#17 0x00007fe5085e8f05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fe5085e9248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fe5085e9304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fe50c3a7016 in QEventDispatcherGlib::processEvents (this=0x7b4660, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#21 0x00007fe50ce0813e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fe50c37738f in QEventLoop::processEvents (this=this@entry=0x7fffb651a880, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fe50c377618 in QEventLoop::exec (this=this@entry=0x7fffb651a880, flags=...) at kernel/qeventloop.cpp:204
#24 0x00007fe50c37ccf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#25 0x00007fe50cd60ffc in QApplication::exec () at kernel/qapplication.cpp:3828
#26 0x000000000040809e in main (argc=<optimized out>, argv=<optimized out>) at ../../shell/main.cpp:94

Reported using DrKonqi
Comment 1 Albert Astals Cid 2013-10-15 22:41:48 UTC
you are searching while the document is being reloaded or after?
Comment 2 Moritz Ulmer 2013-10-16 14:37:35 UTC
It is not clear, in trying to reproduce the bug i hold the enter button pressed to continuously search for the next term in a document ~30 pages long. I have tried reproducing the bug by replacing a different much longer (~300 page) document while it was searching, but with no success. After automatically reloading the document and then searching, doesn't seem to be casing any problems.
Comment 3 Albert Astals Cid 2013-10-16 21:37:42 UTC
Ok, so not easy to repro then. Will try looking at the backtrace and see if we can get it to make any sense.

Thank for the report :-)
Comment 4 Luigi Toscano 2014-05-08 15:23:17 UTC
Some changes related to reloading landed recently in the code, could you please try again with the latest versions of Okular?
Comment 5 Albert Astals Cid 2017-03-28 22:24:15 UTC
No answer for years