Summary: | Crash on closing Okular | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Kerry N <mothlight> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid, m.weghorn, mothlight, simonandric5 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Kerry N
2018-01-24 23:28:07 UTC
Can you reproduce this either every single time or relatively often? 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
Do yo get the crash with other PDF files? I.e. does it only crash with that one file or with all of them? 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. (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? 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. 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. Then it's already fixed. |