Bug 357430 - Okular crashed when activating “fit width”
Summary: Okular crashed when activating “fit width”
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.22.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-01-02 14:29 UTC by Martin Ueding
Modified: 2018-11-03 09:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ueding 2016-01-02 14:29:22 UTC
Application: okular (0.22.2)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

I edit a LaTeX document that is compiled automatically in the background with `latexmk -pdf -pvc` which uses inotify and runs `pdflatex`. So the document has been reloaded a lot of times.

To see some part of an equation more clearly I zoomed in on it by holding the mouse wheel and moving the mouse. Then I took a raster image using the right mouse button. Holding that button I selected some area and stored that as PNG image. A while later I wanted to continue editing and right-clicked into the document. In the context menu I selected “fit width”. Okular instantly crashed as I selected that menu item.

Unfortunately I do not remember exactly whether it was compiling in the background. Then perhaps this action is overlaid with the reloading and then some race condition occured.

So I would assume that the resizing crashed it. I have tried to zoom in into other documents and selecting “fit width” again without a problem. This problem has not occured before at all.

My system is Fedora 23 with RPM Fusion. I use plain Awesome WM without any desktop environment.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f4a9fd900 (LWP 4937))]

Thread 2 (Thread 0x7f3f2907b700 (LWP 11454)):
#0  0x00007f3f469a5ffd in poll () at /lib64/libc.so.6
#1  0x00007f3f424bd16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f3f424bd27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f3f47b7aeae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#4  0x00007f3f47b49151 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#5  0x00007f3f47b494c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#6  0x00007f3f47a38a89 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x00007f3f47b29223 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4
#8  0x00007f3f47a3b37c in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4
#9  0x00007f3f4779960a in start_thread () at /lib64/libpthread.so.0
#10 0x00007f3f469b1a9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f3f4a9fd900 (LWP 4937)):
[KCrash Handler]
#6  0x00007f3f2e96b903 in Okular::Page::number() const () at /lib64/libokularcore.so.6
#7  0x00007f3f2ec2f5e7 in Okular::Part::slotShowMenu(Okular::Page const*, QPoint const&) () at /usr/lib64/kde4/okularpart.so
#8  0x00007f3f2ec3bff8 in Okular::Part::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.87] () at /usr/lib64/kde4/okularpart.so
#9  0x00007f3f47b5ea80 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4
#10 0x00007f3f2ec9dee9 in PageView::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/kde4/okularpart.so
#11 0x00007f3f48861140 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4
#12 0x00007f3f48c2670e in QFrame::event(QEvent*) () at /lib64/libQtGui.so.4
#13 0x00007f3f2eca0dc6 in PageView::viewportEvent(QEvent*) () at /usr/lib64/kde4/okularpart.so
#14 0x00007f3f47b4aa46 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib64/libQtCore.so.4
#15 0x00007f3f4880a91c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4
#16 0x00007f3f48811956 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4
#17 0x00007f3f4959654a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5
#18 0x00007f3f47b4a8dd in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4
#19 0x00007f3f48810f5d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () at /lib64/libQtGui.so.4
#20 0x00007f3f4888b862 in QETWidget::translateMouseEvent(_XEvent const*) () at /lib64/libQtGui.so.4
#21 0x00007f3f4888a22d in QApplication::x11ProcessEvent(_XEvent*) () at /lib64/libQtGui.so.4
#22 0x00007f3f488b3249 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtGui.so.4
#23 0x00007f3f424bce3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#24 0x00007f3f424bd1d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#25 0x00007f3f424bd27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#26 0x00007f3f47b7ae8e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#27 0x00007f3f488b33e6 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtGui.so.4
#28 0x00007f3f47b49151 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#29 0x00007f3f47b494c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#30 0x00007f3f47b4f069 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#31 0x0000561e075082eb in main ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-11-01 13:52:15 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Martin Ueding 2018-11-03 09:42:55 UTC
This issue did not occur since I have reported it, so I presume that it has been fixed or not been triggered again.