Bug 204275 - opening multiple ps files at once with okular crashes okular
Summary: opening multiple ps files at once with okular crashes okular
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: PS backend (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
: 202500 224484 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-18 14:09 UTC by Oliver Putz
Modified: 2010-01-27 17:40 UTC (History)
2 users (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 Oliver Putz 2009-08-18 14:09:29 UTC
Application that crashed: okular
Version of the application: 0.9
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.1
Operating System: Linux 2.6.28-gentoo-r6 x86_64

What I was doing when the application crashed:
Steps to reproduce:

1) Select multiple ps files
2) Right click -> open with -> okular
3) See okular (KDE-4.3.0) crash with the backtrace below

Note: Opening multiple pdf files at once works

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
[Current thread is 0 (LWP 27480)]

Thread 2 (Thread 0x7f54baefe950 (LWP 27487)):
[KCrash Handler]
#5  0x00007f54bd18dc82 in psdocdestroy (doc=0x7f54cc3af990) at ps.c:1335
#6  0x00007f54bd18d076 in spectre_page_free (page=0xd00dc0) at spectre-page.c:66
#7  0x00007f54bd3a934b in GSRendererThread::run (this=0xd13450) at /tmp/portage/kde-base/okular-4.3.0/work/okular-4.3.0/okular/generators/spectre/rendererthread.cpp:104
#8  0x00007f54cc6578d9 in QThreadPrivate::start (arg=0xd13450) at thread/qthread_unix.cpp:189
#9  0x00007f54cc3e7017 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#10 0x00007f54caeb448d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f54ce763750 (LWP 27480)):
#0  0x00007f54cc3ed88b in read () from /lib/libpthread.so.0
#1  0x00007f54c844529a in IA__g_main_context_check (context=0x62d520, max_priority=2147483647, fds=0xcf9470, n_fds=6) at gmain.c:2605
#2  0x00007f54c8445d71 in g_main_context_iterate (context=0x62d520, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2775
#3  0x00007f54c844604b in IA__g_main_context_iteration (context=0x62d520, may_block=1) at gmain.c:2841
#4  0x00007f54cc750e9f in QEventDispatcherGlib::processEvents (this=0x6115c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#5  0x00007f54cbb0385f in QGuiEventDispatcherGlib::processEvents (this=0x3, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#6  0x00007f54cc72a3f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -696618160}) at kernel/qeventloop.cpp:149
#7  0x00007f54cc72a585 in QEventLoop::exec (this=0x7fffd67a7390, flags={i = -696618080}) at kernel/qeventloop.cpp:196
#8  0x00007f54cc72c61c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#9  0x000000000040884b in main (argc=<value optimized out>, argv=<value optimized out>) at /tmp/portage/kde-base/okular-4.3.0/work/okular-4.3.0/okular/shell/main.cpp:81

Reported using DrKonqi
Comment 1 Oliver Putz 2009-08-18 14:13:00 UTC
Edit: Seems like "multiple" in my case actually means >= 3
Comment 2 Albert Astals Cid 2009-08-24 01:06:14 UTC
Pino didn't we discuss this already and we came up with a locking mechanism? Or did never really implement it?
Comment 3 Pino Toscano 2009-08-27 12:17:14 UTC
(In reply to comment #2)
> Pino didn't we discuss this already and we came up with a locking mechanism? Or
> did never really implement it?

Should be in trunk (locked queue'ing system), will backport if stable enough.
Comment 4 Pino Toscano 2009-08-27 12:52:27 UTC
*** Bug 202500 has been marked as a duplicate of this bug. ***
Comment 5 Pino Toscano 2009-12-26 18:43:50 UTC
This should have been fixed for KDE 4.3.3 (Okular 0.9.3).
If there are still problems, feel free to ping or reopen.
Comment 6 Pino Toscano 2010-01-27 17:40:15 UTC
*** Bug 224484 has been marked as a duplicate of this bug. ***