Application that crashed: okular Version of the application: 0.9.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-19-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: The same of the object -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #6 0x005aa422 in __kernel_vsyscall () #7 0x03c7d4d1 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x03c80932 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x03cb3ee5 in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0x03cbdff1 in ?? () from /lib/tls/i686/cmov/libc.so.6 #11 0x03cc0be3 in ?? () from /lib/tls/i686/cmov/libc.so.6 #12 0x03cc2898 in malloc () from /lib/tls/i686/cmov/libc.so.6 #13 0x00ccb6bd in qMalloc(unsigned int) () from /usr/lib/libQtCore.so.4 #14 0x00cd35f6 in QByteArray::QByteArray(int, char) () from /usr/lib/libQtCore.so.4 #15 0x00cc84a9 in qt_error_string(int) () from /usr/lib/libQtCore.so.4 #16 0x00cd020f in ?? () from /usr/lib/libQtCore.so.4 #17 0x00cd0390 in ?? () from /usr/lib/libQtCore.so.4 #18 0x00ccbb82 in QMutex::lock() () from /usr/lib/libQtCore.so.4 #19 0x06f604c0 in Okular::Document::closeDocument() () from /usr/lib/libokularcore.so.1 #20 0x02e9d3fd in ?? () from /usr/lib/kde4/okularpart.so #21 0x0038d6f6 in KParts::ReadOnlyPart::openUrl(KUrl const&) () from /usr/lib/libkparts.so.4 #22 0x02eaa08f in ?? () from /usr/lib/kde4/okularpart.so #23 0x02eaa774 in ?? () from /usr/lib/kde4/okularpart.so #24 0x00dd7263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #25 0x00dd76d8 in QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4 #26 0x00fcf9b1 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4 #27 0x00fd0f32 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4 #28 0x00fd3a18 in QAction::event(QEvent*) () from /usr/lib/libQtGui.so.4 #29 0x009dbeb3 in KAction::event(QEvent*) () from /usr/lib/libkdeui.so.5 #30 0x00fd5f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #31 0x00fdd67c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #32 0x00ac2bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #33 0x00dc16cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #34 0x0100edfd in ?? () from /usr/lib/libQtGui.so.4 #35 0x01010c7e in ?? () from /usr/lib/libQtGui.so.4 #36 0x00fdea0d in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #37 0x00ac2bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #38 0x00dc16cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #39 0x00fd6e2e in ?? () from /usr/lib/libQtGui.so.4 #40 0x01073440 in ?? () from /usr/lib/libQtGui.so.4 #41 0x01075989 in ?? () from /usr/lib/libQtGui.so.4 #42 0x01049ed7 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #43 0x01077502 in ?? () from /usr/lib/libQtGui.so.4 #44 0x018afe88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #45 0x018b3730 in ?? () from /lib/libglib-2.0.so.0 #46 0x018b3863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #47 0x00dec02c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #48 0x01076be5 in ?? () from /usr/lib/libQtGui.so.4 #49 0x00dbfc79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #50 0x00dc00ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #51 0x00dc253f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #52 0x00fd5dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #53 0x0804eec9 in _start () Reported using DrKonqi
- Does the application crash again if you repeat the situation you described ? - Was some application using a lot of memory ? I wonder if it could be related to bug 196207. Regards
I'll don't know if my problem can be associated to 196207 but I'll Hoe it. ^__^ The application does not crash every time with the same file and only some file had the problem. Approssimatively okular crash 3 on 5 times on the same file. Two process had great memory and process use: okular and gs (of cups-pdf) Thanks
*** Bug 248738 has been marked as a duplicate of this bug. ***
Can you still reproduce this behaviour? If you can, can you please install debugging symbols so your backtraces make sense? Thanks for caring about Okular :-)
Sorry. It was two years and three SO ago. ^___^
I know it was long time ago, but your answer doesn't answer my question: Can you still reproduce this behaviour?
No, I'm on a totally different OS and Kernel. I cant' reproduce it in any way
User can't reproduce anymore nor can we.