Bug 382725 - Okular crashes when rotating view in multi-page pdf document
Summary: Okular crashes when rotating view in multi-page pdf document
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 1.0.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 374539 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-07-25 18:27 UTC by ST
Modified: 2017-11-24 22:28 UTC (History)
4 users (show)

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


Attachments
AX_INSTRUCTION_MANUAL_en.pdf (2.25 MB, application/pdf)
2017-07-29 21:00 UTC, ST
Details
before rotating.png (673.78 KB, image/png)
2017-07-29 21:00 UTC, ST
Details
stretched after commenced rotating.png (626.55 KB, image/png)
2017-07-29 21:00 UTC, ST
Details
attachment-12094-0.html (872 bytes, text/html)
2017-07-29 21:18 UTC, ST
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ST 2017-07-25 18:27:44 UTC
Okular 1.0.3 freezed & crashed, when I've tried to rotate 90 deg. page-view in multipage pdf document

On page pdf: mixed graphic/text content
Comment 1 Albert Astals Cid 2017-07-29 10:22:10 UTC
Can you reproduce this every time or did it just happen once?
Comment 2 ST 2017-07-29 21:00:47 UTC
Created attachment 106958 [details]
AX_INSTRUCTION_MANUAL_en.pdf

Hi Albert,


Unfortunately this happened few times. I am PC-user, not programmer.

I can only describe what happened.

Today I have tried to rotate page-10 in attached pdf document.

1st test: after clicking on "rotate right", page stretched to window 
size and after sometime of "frozen" condition Okular closed by itself.

2nd test with same page - all OK

3rd and 4th test- Okular immediately closed after clicking on "rotate" 
in menu

Remark: same page of this document was "rotated" many times in Adobe 
reader without problems, so I presume pdf file is not a cause for mishap.

Best regards

Sergey


On 29/07/17 11:22, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=382725
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Resolution|---                         |WAITINGFORINFO
>                   CC|                            |aacid@kde.org
>               Status|UNCONFIRMED                 |NEEDSINFO
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Can you reproduce this every time or did it just happen once?
>
Comment 3 ST 2017-07-29 21:00:48 UTC
Created attachment 106959 [details]
before rotating.png
Comment 4 ST 2017-07-29 21:00:48 UTC
Created attachment 106960 [details]
stretched after commenced rotating.png
Comment 5 Albert Astals Cid 2017-07-29 21:11:27 UTC
Did the drkonqui crash handler appear when it crashed? or just okular disappears?
Comment 6 ST 2017-07-29 21:18:07 UTC
Created attachment 106961 [details]
attachment-12094-0.html

Only Okular



On 29/07/17 22:11, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=382725
>
> --- Comment #5 from Albert Astals Cid <aacid@kde.org> ---
> Did the drkonqui crash handler appear when it crashed? or just okular
> disappears?
>
Comment 7 Albert Astals Cid 2017-07-29 22:01:39 UTC
Without more information is hard to figure out what is wrong, please try reading 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

and see if you can give a backtrace with the information of what is crashing, i know it's a bit complicated if you're not a developer, ask if there's something you dont' understand.
Comment 8 Albert Astals Cid 2017-09-14 18:48:54 UTC
Sergey said it works for him fine now in a private email.
Comment 9 Ian Borg 2017-11-01 02:15:49 UTC
I can confirm this bug on a current OpenSUSE Leap 42.3 system. 

However, it only happens when I launch the program from the main Application Launcher in the lower left hand corner. When I open a multi page doc and rotate right or left the Okular window just closes, with no other dialog at all.
When I run the program under gdb, it does not crash when rotating. 
It does, however lock up after a while, usually when scrolling through pages using the navigation bar set to thumbnails. 
gdb shows an error in the trace output close to where the program is started, plus a segfault where it locks up. I'm including them in case they have anything to do with the rotation issue, I have no idea:

1. error when okular is started or re-started:

(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/okular 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffea9c3700 (LWP 19398)]
[New Thread 0x7fffe6115700 (LWP 19399)]
Detaching after fork from child process 19402.
Detaching after fork from child process 19403.
[New Thread 0x7fffccbf2700 (LWP 19405)]
[New Thread 0x7fffc83f1700 (LWP 19406)]
[Thread 0x7fffc83f1700 (LWP 19406) exited]
[Thread 0x7fffccbf2700 (LWP 19405) exited]
QXcbConnection: XCB error: 3 (BadWindow), sequence: 4859, resource id: 36951301, major code: 40 (TranslateCoords), minor code: 0
[New Thread 0x7fffccbf2700 (LWP 19408)]
[New Thread 0x7fffc83f1700 (LWP 19409)]



2: Segfault once the pgm locks up:

...etc etc
[Thread 0x7fffb6b69700 (LWP 19640) exited]
[New Thread 0x7fffb6b69700 (LWP 19641)]
[Thread 0x7fffb6b69700 (LWP 19641) exited]
[New Thread 0x7fffb6b69700 (LWP 19642)]
[Thread 0x7fffb6b69700 (LWP 19642) exited]

Thread 72 "Queue(0x12e7190" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc83f1700 (LWP 19475)]
0x00007ffff566d8b0 in vtable for QPaintDevice () from /usr/lib64/libQt5Gui.so.5
(gdb)
Comment 10 Albert Astals Cid 2017-11-02 16:49:21 UTC
Git commit 662fa69a2dcc0c1403b1773262368943d5cacd52 by Albert Astals Cid.
Committed on 02/11/2017 at 16:49.
Pushed by aacid into branch 'Applications/17.08'.

Fix crash on rotation jobs

We don't need to delete the threadweaver job, threadweaver does it by itself,
and if we call deleteLater it may happen that the main thread deletes it
and then when the threadweaver thread tries to call the delete things are
gone and it goes kaboom

M  +0    -2    core/pagecontroller.cpp

https://commits.kde.org/okular/662fa69a2dcc0c1403b1773262368943d5cacd52
Comment 11 null 2017-11-24 22:28:48 UTC
*** Bug 374539 has been marked as a duplicate of this bug. ***