Summary: | Okular crash | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | hellsdottir |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid |
Priority: | NOR | ||
Version: | 0.12.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
run on dvi of a 3-page document with no images
run on dvi of a 3-page document with no images immediately after the previous entry |
Description
hellsdottir
2012-02-03 02:19:28 UTC
You say it can be reproduced all the time, does it crash with all documents or just with a specific one? 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. > Can you run valgrind okular myfile.dvi and attach its output? 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. > You did not attach anything to the bug. ? 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. > Please use the web interface at https://bugs.kde.org/show_bug.cgi?id=293181 to attach the files 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.
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.
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. Does this still happen in newer KDE/Okular versions? No answer in 3 months, I'll assume it's fixed, please reopen if you can still reproduce |