Bug 389385 - Crash on closing Okular
Summary: Crash on closing Okular
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-01-24 23:28 UTC by Kerry N
Modified: 2018-04-06 11:30 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.02 KB, text/plain)
2018-01-24 23:51 UTC, Kerry N
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kerry N 2018-01-24 23:28:07 UTC
Application: okular (0.24.2)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-98-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Open Okular via Mendeley desktop (open file externally)
Read the article
Close using the X button
Crash report appears.

-- Backtrace:
Application: Okular (okular), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f909124f428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007f909125102a in __GI_abort () at abort.c:89
#8  0x00007f90912917ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f90913aaed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007f909129a37a in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f90913aafe8 "double free or corruption (out)", action=3) at malloc.c:5006
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
#11 0x00007f909129e53c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
#12 0x00007f908241c264 in ?? () from /usr/lib/libokularcore.so.7
#13 0x00007f908241c324 in Okular::TextPage::~TextPage() () from /usr/lib/libokularcore.so.7
#14 0x00007f908240f757 in ?? () from /usr/lib/libokularcore.so.7
#15 0x00007f9082411e13 in Okular::Page::~Page() () from /usr/lib/libokularcore.so.7
#16 0x00007f90823fe9c6 in Okular::Document::closeDocument() () from /usr/lib/libokularcore.so.7
#17 0x00007f90826d67b4 in Okular::Part::closeUrl(bool) () from /usr/lib/kde4/okularpart.so
#18 0x000000000041039e in ?? ()
#19 0x0000000000410509 in ?? ()
#20 0x00007f9091d8ddd8 in QObject::event (this=this@entry=0x137b640, e=e@entry=0x2040400) at kernel/qobject.cpp:1203
#21 0x00007f90927dad3c in QWidget::event (this=this@entry=0x137b640, event=event@entry=0x2040400) at kernel/qwidget.cpp:8859
#22 0x00007f9092bbe9b3 in QMainWindow::event (this=this@entry=0x137b640, event=event@entry=0x2040400) at widgets/qmainwindow.cpp:1478
#23 0x00007f90935b1131 in KMainWindow::event (this=this@entry=0x137b640, ev=ev@entry=0x2040400) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/kdeui/widgets/kmainwindow.cpp:1126
#24 0x00007f90935ee879 in KXmlGuiWindow::event (this=0x137b640, ev=0x2040400) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/kdeui/xmlgui/kxmlguiwindow.cpp:126
#25 0x00007f9092783fdc in QApplicationPrivate::notify_helper (this=this@entry=0x11d0120, receiver=receiver@entry=0x137b640, e=e@entry=0x2040400) at kernel/qapplication.cpp:4570
#26 0x00007f909278af16 in QApplication::notify (this=this@entry=0x7ffe5f38c360, receiver=receiver@entry=0x137b640, e=e@entry=0x2040400) at kernel/qapplication.cpp:4356
#27 0x00007f90934e964a in KApplication::notify (this=0x7ffe5f38c360, receiver=0x137b640, event=0x2040400) at /build/kde4libs-_S4zyz/kde4libs-4.14.16/kdeui/kernel/kapplication.cpp:311
#28 0x00007f9091d7390d in QCoreApplication::notifyInternal (this=0x7ffe5f38c360, receiver=receiver@entry=0x137b640, event=event@entry=0x2040400) at kernel/qcoreapplication.cpp:955
#29 0x00007f9091d773c6 in QCoreApplication::sendEvent (event=0x2040400, receiver=0x137b640) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x11936b0) at kernel/qcoreapplication.cpp:1579
#31 0x00007f9091d776a3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1472
#32 0x00007f9091da413e in QCoreApplication::sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#33 postEventSourceDispatch (s=0x11d6200) at kernel/qeventdispatcher_glib.cpp:300
#34 0x00007f908e3ed127 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007f908e3ed380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007f908e3ed42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007f9091da42ae in QEventDispatcherGlib::processEvents (this=0x1194b90, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#38 0x00007f9092831616 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#39 0x00007f9091d7218f in QEventLoop::processEvents (this=this@entry=0x7ffe5f38c2c0, flags=...) at kernel/qeventloop.cpp:149
#40 0x00007f9091d724f5 in QEventLoop::exec (this=this@entry=0x7ffe5f38c2c0, flags=...) at kernel/qeventloop.cpp:204
#41 0x00007f9091d784b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1227
#42 0x0000000000409858 in ?? ()
#43 0x00007f909123a830 in __libc_start_main (main=0x409410, argc=6, argv=0x7ffe5f38c478, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe5f38c468) at ../csu/libc-start.c:291
#44 0x000000000040b489 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 379497.

Possible duplicates by query: bug 389090, bug 387393, bug 381268, bug 379497, bug 375933.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2018-01-24 23:47:58 UTC
Can you reproduce this either every single time or relatively often?
Comment 2 Kerry N 2018-01-24 23:51:19 UTC
Created attachment 110100 [details]
New crash information added by DrKonqi

okular (0.24.2) on KDE Platform 4.14.16 using Qt 4.8.7

- What I was doing when the application crashed:
Followed the same procedure, opening the same PDF in the same way and received the same crash when closing it.

-- Backtrace (Reduced):
#6  0x00007f458a441428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007f458a44302a in __GI_abort () at abort.c:89
[...]
#9  0x00007f458a48c37a in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f458a59cfe8 "double free or corruption (out)", action=3) at malloc.c:5006
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
#11 0x00007f458a49053c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
Comment 3 Albert Astals Cid 2018-01-24 23:57:22 UTC
Do yo get the crash with other PDF files? I.e. does it only crash with that one file or with all of them?
Comment 4 Kerry N 2018-01-25 00:03:37 UTC
I can consistently make it crash if I use the page arrows < > to page through the document. Using them all the way to the very bottom of the document seems to make Okular unhappy. Or using them to scroll back and forth very quickly. I could reproduce this with two different documents.
Comment 5 Michael Weghorn 2018-01-25 11:46:51 UTC
(In reply to Kerry N from comment #2)
> [...]
> okular (0.24.2) on KDE Platform 4.14.16 using Qt 4.8.7
> 
> [...]

The reported Okular version is really old and there have been a lot of fixes to Okular in the meantime. Do you have the chance to test wether the problem still exists with a more recent version of Okular?
Comment 6 Albert Astals Cid 2018-01-25 20:51:49 UTC
I guess it also would be helpful if you can attach a file that has this problem for you and we test if it happens in newer versions.
Comment 7 Kerry N 2018-01-25 22:59:39 UTC
This is the article (too large to attach)
https://www.dropbox.com/s/w9ujomep8mo1w2h/okular_article.pdf?dl=0

I can pretty consistently crash okular 4:15.12.3-0ubunt amd64 by just quickly pressing the forward and backward arrows. By the time I've gone back and forth through the document 1 or 2 times, it has crashed.

I tried the same document with okular-16.12.3-1.fc26-x86_64 but wasn't able to reproduce the problem.
Comment 8 Albert Astals Cid 2018-01-25 23:45:29 UTC
Then it's already fixed.