Bug 157559 - okular crashes when loading pdf file and scrolling at the same time
Summary: okular crashes when loading pdf file and scrolling at the same time
Status: RESOLVED WORKSFORME
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:
Depends on:
Blocks:
 
Reported: 2008-02-09 21:59 UTC by Sebastian
Modified: 2008-12-20 04:10 UTC (History)
1 user (show)

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 Sebastian 2008-02-09 21:59:21 UTC
Version:            (using KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

1. open pdf document with okular
2. modify this pdf document, so okular has to reload it
3. use the scroll bar while okular is reloading file
=> okular crashes with "signal 6 (SIGABRT)"

Comment: This is the version of KDE 4.0.1 (it wasn't possible to select this version via drop down menu in the bug tracking system)

Backtrace:

0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 16602)]

Thread 2 (Thread -1295103088 (LWP 16809)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6b76676 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6d7131d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7dd329d in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb4d0104d in ?? () from /usr/lib/kde4/lib/libthreadweaver.so.4
#5  0x08352f88 in ?? ()
#6  0x083a7fd8 in ?? ()
#7  0xffffffff in ?? ()
#8  0x00000010 in ?? ()
#9  0x083fd6a0 in ?? ()
#10 0xb2ce42c4 in ?? ()
#11 0xb2ce4258 in ?? ()
#12 0xb4d05a44 in ?? () from /usr/lib/kde4/lib/libthreadweaver.so.4
#13 0x083fd6a0 in ?? ()
#14 0xb4d0e0b4 in vtable for ThreadWeaver::WeaverInterface ()
   from /usr/lib/kde4/lib/libthreadweaver.so.4
#15 0x083a7fd9 in ?? ()
#16 0xb4d0ea10 in ?? () from /usr/lib/kde4/lib/libthreadweaver.so.4
#17 0x00000000 in ?? ()

Thread 1 (Thread -1236268656 (LWP 16602)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6d236db in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7ab8a6b in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#3  0x000041ab in ?? ()
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Albert Astals Cid 2008-02-09 22:50:30 UTC
All files or a specific file? If it is a specific file can you please attach it?
Comment 2 Sebastian 2008-02-09 22:55:50 UTC
It seems to be with all pdf files.
Comment 3 Albert Astals Cid 2008-02-09 23:18:17 UTC
when do you use the scrollbar? When the document "closes" and you get a "Reloading document"? Before that? After that?
Comment 4 Sebastian 2008-02-09 23:35:25 UTC
it's hard to say, as it happens quite fast...

maybe a little more background information could help:
I'm starting pdflatex in konsole and while latex is still compiling (this sometimes can take some time), I am scrolling in okular to the position, where I expect made my new changes. So, when pdflatex has done its job (and has updated the pdf file => reloading sequence in okular is starting) and I'm still "scrolling around", okular crashes.

I can't be sure, but I assume, okular first gets the signal "hey, someone updated your pdf file". Then it closes the file in order in order to reopen it. Reopening takes some time, so while okular is still busy, reopening the file, the progress bar signal of my scrolling action is causing some error, as it says "scroll up 5 lines, please" but there is nothing to scroll while loading. - But, as I said, it's just a guess!

I just tried the same thing with good old kpdf and there weren't any problems. It seems (another guess, only!) that kpdf doesn't actually close/remove the pdf file before reloading. It just keeps the old version open, until the new version is fully available and can be replaced for the old one without any delay.

Hoping, this helps you a bit. :)
Comment 5 Dario Andres 2008-08-01 22:02:56 UTC
Can you still reproduce this bug with a recent version of KDE like 4.0.5 or 4.1 ?
Comment 6 Dario Andres 2008-12-20 04:10:59 UTC
No response. If this is still a problem in a current version, please reopen with more information