Bug 293181 - Okular crash
Summary: Okular crash
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.12.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-03 02:19 UTC by hellsdottir
Modified: 2012-11-14 14:17 UTC (History)
1 user (show)

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


Attachments
run on dvi of a 3-page document with no images (3.41 KB, application/octet-stream)
2012-02-17 23:18 UTC, hellsdottir
Details
run on dvi of a 3-page document with no images immediately after the previous entry (3.41 KB, application/octet-stream)
2012-02-17 23:19 UTC, hellsdottir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hellsdottir 2012-02-03 02:19:28 UTC
Application: okular (0.12.5)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
I tried to open a DVI document - that's all. I tried Ubuntu 11.10, did not like it. I reinstalled 11.04 over 11.10. I keep a separate partition for my home directory. Kile and all DVI and LaTeX operations were fantastically slow and often crashed. I formatted my root drive, reinstalled 11.04 from scratch, mounted my same home partition, and still have the same problems. Compiling a 3-page document of only text now takes upwards of 3 minutes (regardless of the LaTeX compiler I use) and opening DVI files or trying to convert them often results in a crash after using about 1GB of memory. 

Also... this bug reporting process is terrible. I needed to install packages, create accounts (with no control over the username - it uses my email address - which I HATE) and generally had to bounce around and figure out what this tool wanted in order to proceed - which is exactly what you don't want for an automatic error-reporting tool. If it isn't one-click easy you'll have very few users actually go through the pain of using it. I only did in order to give you this feedback. The next time it pops up, it's getting dismissed.

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
[Current thread is 1 (Thread 0x7faaf901c780 (LWP 2041))]

Thread 2 (Thread 0x7faaed89a700 (LWP 2042)):
#0  0x00007faaf629ff03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007faaf319c104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007faaf319c9f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007faaee1f9c44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007faaf31c33e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007faaf3667d8c in start_thread (arg=0x7faaed89a700) at pthread_create.c:304
#6  0x00007faaf62ad04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7faaf901c780 (LWP 2041)):
[KCrash Handler]
#6  0x00007faada9e7b54 in Okular::Generator::document (this=0xc2b470) at ../../okular/core/generator.cpp:373
#7  0x00007faad61e481e in DviGenerator::loadDocument (this=0xc2b470, fileName=..., pagesVector=...) at ../../../../okular/generators/dvi/generator_dvi.cpp:120
#8  0x00007faada9d7e6a in Okular::DocumentPrivate::openDocumentInternal (this=0xa4f5f0, offer=<value optimized out>, isstdin=<value optimized out>, docFile=..., filedata=...) at ../../okular/core/document.cpp:674
#9  0x00007faada9e0951 in Okular::Document::openDocument (this=0xa49240, docFile=..., url=<value optimized out>, _mime=<value optimized out>) at ../../okular/core/document.cpp:1632
#10 0x00007faadac82581 in Okular::Part::openFile (this=0xa360d0) at ../../okular/part.cpp:955
#11 0x00007faaf8c0aab0 in KParts::ReadOnlyPartPrivate::openLocalFile (this=0xa348d0) at ../../kparts/part.cpp:592
#12 0x00007faaf8c0b0f4 in KParts::ReadOnlyPart::openUrl (this=0xa360d0, url=...) at ../../kparts/part.cpp:556
#13 0x00007faadac7b225 in Okular::Part::openUrl (this=0xa360d0, _url=<value optimized out>) at ../../okular/part.cpp:1076
#14 0x0000000000408ce4 in Shell::openUrl (this=0xa18970, url=...) at ../../../okular/shell/shell.cpp:134
#15 0x000000000040a84c in Shell::qt_metacall (this=0xa18970, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfe7d0) at ./shell.moc:94
#16 0x00007faaf6c4749a in QObject::event (this=0xa18970, e=<value optimized out>) at kernel/qobject.cpp:1226
#17 0x00007faaf764367d in QWidget::event (this=0xa18970, event=0xbfe470) at kernel/qwidget.cpp:8718
#18 0x00007faaf7a0fc0b in QMainWindow::event (this=0xa18970, event=0xbfe470) at widgets/qmainwindow.cpp:1480
#19 0x00007faaf8411afe in KXmlGuiWindow::event (this=0xa18970, ev=0xbfe470) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126
#20 0x00007faaf75f29f4 in QApplicationPrivate::notify_helper (this=0x76dca0, receiver=0xa18970, e=0xbfe470) at kernel/qapplication.cpp:4462
#21 0x00007faaf75f73ba in QApplication::notify (this=<value optimized out>, receiver=0xa18970, e=0xbfe470) at kernel/qapplication.cpp:4341
#22 0x00007faaf83166c6 in KApplication::notify (this=0x7fff1463bd40, receiver=0xa18970, event=0xbfe470) at ../../kdeui/kernel/kapplication.cpp:311
#23 0x00007faaf6c3349c in QCoreApplication::notifyInternal (this=0x7fff1463bd40, receiver=0xa18970, event=0xbfe470) at kernel/qcoreapplication.cpp:731
#24 0x00007faaf6c36c25 in sendEvent (receiver=0x0, event_type=0, data=0x723b60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x723b60) at kernel/qcoreapplication.cpp:1372
#26 0x00007faaf6c5e253 in sendPostedEvents (s=0x771160) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x771160) at kernel/qeventdispatcher_glib.cpp:277
#28 0x00007faaf319bbcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007faaf319c3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007faaf319c639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007faaf6c5e3ef in QEventDispatcherGlib::processEvents (this=0x723340, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#32 0x00007faaf769c4de in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007faaf6c32882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007faaf6c32abc in QEventLoop::exec (this=0x7fff1463bcc0, flags=...) at kernel/qeventloop.cpp:201
#35 0x00007faaf6c36ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#36 0x000000000040812e in main (argc=2, argv=<value optimized out>) at ../../../okular/shell/main.cpp:85

Reported using DrKonqi
Comment 1 Albert Astals Cid 2012-02-03 18:23:28 UTC
You say it can be reproduced all the time, does it crash with all documents or just with a specific one?
Comment 2 hellsdottir 2012-02-13 22:43:04 UTC
  It happens on every single document.

  It isn't really an Okular problem, something is wrong with dvi
rendering/computation in Ubuntu 11.04. It takes me about 30 minutes to
build a 3-page text-only document.

  Linux *^*^*^ 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux


On 2/3/12, Albert Astals Cid <tsdgeos@terra.es> wrote:
> https://bugs.kde.org/show_bug.cgi?id=293181
>
>
>
>
>
> --- Comment #1 from Albert Astals Cid <tsdgeos terra es>  2012-02-03
> 18:23:28 ---
> You say it can be reproduced all the time, does it crash with all documents
> or
> just with a specific one?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Albert Astals Cid 2012-02-13 23:01:12 UTC
Can you run 
  valgrind okular myfile.dvi
and attach its output?
Comment 4 hellsdottir 2012-02-14 21:42:01 UTC
  Here you are.

  Valgrindoutput is the output of a cold run without okular having been run.

  Valgrindoutput1 is the output of a run immediately after the
valgrindoutput run. Okular itself came up much faster, so thre was much
more of the program in memory.

  There was no crash, however both took a very long time to render.


On Mon, Feb 13, 2012 at 6:01 PM, Albert Astals Cid <tsdgeos@terra.es> wrote:

> https://bugs.kde.org/show_bug.cgi?id=293181
>
>
>
>
>
> --- Comment #3 from Albert Astals Cid <tsdgeos terra es>  2012-02-13
> 23:01:12 ---
> Can you run
>  valgrind okular myfile.dvi
> and attach its output?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 5 Albert Astals Cid 2012-02-14 21:48:59 UTC
You did not attach anything to the bug.
Comment 6 hellsdottir 2012-02-14 23:07:16 UTC
  ?

  Here are the two files again.



On Tue, Feb 14, 2012 at 4:49 PM, Albert Astals Cid <tsdgeos@terra.es> wrote:

> https://bugs.kde.org/show_bug.cgi?id=293181
>
>
>
>
>
> --- Comment #5 from Albert Astals Cid <tsdgeos terra es>  2012-02-14
> 21:48:59 ---
> You did not attach anything to the bug.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 7 Albert Astals Cid 2012-02-14 23:20:57 UTC
Please use the web interface at https://bugs.kde.org/show_bug.cgi?id=293181 to attach the files
Comment 8 hellsdottir 2012-02-17 23:18:21 UTC
Created attachment 68890 [details]
run on dvi of a 3-page document with no images

I hate email addresses as logins. I hate requiring adding information that already exists elsewhere so I can supply information I was asked for. I dislike email forwarding that isn't fully reflexive.
Comment 9 hellsdottir 2012-02-17 23:19:07 UTC
Created attachment 68891 [details]
run on dvi of a 3-page document with no images immediately after the previous entry

I hate email addresses as logins. I hate requiring adding information that already exists elsewhere so I can supply information I was asked for. I dislike email forwarding that isn't fully reflexive.
Comment 10 Albert Astals Cid 2012-02-17 23:30:50 UTC
Those valgrind traces show no problem, in fact Okular did not crash at all when run through valgrind, right?

And by the way, stop complaining, it's make me wanting to ignore you more and more.
Comment 11 Albert Astals Cid 2012-08-09 21:10:57 UTC
Does this still happen in newer KDE/Okular versions?
Comment 12 Albert Astals Cid 2012-11-14 14:17:01 UTC
No answer in 3 months, I'll assume it's fixed, please reopen if you can still reproduce