GNOME Bugzilla – Bug 311233
Evince crashes with .ps files produced by gnuplot
Last modified: 2006-01-12 22:23:04 UTC
Distribution: Fedora Core release 4 (Stentz) Package: evince Severity: critical Version: GNOME2.10.0 0.3.x Gnome-Distributor: Red Hat, Inc Synopsis: Evince crashes with .ps files produced by gnuplot Bugzilla-Product: evince Bugzilla-Component: general Bugzilla-Version: 0.3.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: (evince:3177): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `EvJobRender' ** (evince:3177): CRITICAL **: ev_page_cache_get_size: assertion `page >= 0 && page < page_cache->n_pages' failed (evince:3177): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `EvJobRender' ** (evince:3177): CRITICAL **: ev_job_queue_remove_job: assertion `EV_IS_JOB (job)' failed Steps to reproduce the crash: 1. Produce a .ps file with Gnuplot 4.0 2. Have a evince in background 3. Try to reread the file after replot Expected Results: How often does this happen? Systematically after two replots Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209108800 (LWP 3203)] [New Thread -1211233360 (LWP 3204)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00741402 in ?? ()
+ Trace 61935
Thread 1 (Thread -1209108800 (LWP 3203))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-22 08:59 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was manninen@chem.au.dk.
Thanks for the bug report. Can you please attach here (or make available on a web page) a gnuplot-produced .ps with which you get this crash?
Created attachment 49743 [details] tampmag.plt
Created attachment 49744 [details] fig1.ps Both from private mail to bugzilla-daemon.. which we luckily noticed between all the spam.
Could you give the exact command to reproduce the bug please? I'm not very familiar with gnuplot.
This partly works: gnuplot < tampmag.plt It wants the files t1_pao_dist.uns and t2_pao_dist.uns. Can we have that too?
I have made two data files to test. I can't reproduce the bug with my 0.3.2 version. I'm not sure to have understand how reproduce it. - i plot - open fig1.ps - re plot - reopen fig1.ps with the same evince It's here that should crash?
Got the fig1.ps and tampmag.plt from the reporter by mail.
Created attachment 49762 [details] tampmag.plt
Hi, I reply again to this incorrect address as I don't have the private addresses for either of you (Guillaume Desmottes nor Olav Vitters). I'll try to give a combined answer: > I can't reproduce the bug with my 0.3.2 version. > I'm not sure to have understand how reproduce it. > - i plot > - open fig1.ps > - re plot > It's here that should crash? No. Sorry, I was unclear: Just open the .ps file, and try to reread it with Ctrl-R. (I noticed the bug while replotting the script and trying to reread the new .ps file, but I later found out that the bug occurs while re-reading the same, i.e. unmodified .ps file for several times). Repeat that for two or three times and the crash should occur. > Could you give the exact command to reproduce the bug please? > I'm not very familiar with gnuplot. ... > It wants the files t1_pao_dist.uns and t2_pao_dist.uns. Can we have that too? Just typing "gnuplot tampmag.plt" should do. Please find those data files attached. > Both from private mail to bugzilla-daemon.. which we luckily noticed between > all the spam. Yes, I _did_ notice the "DO NOT reply" :-) But Christian Persch asked me the .ps file and didn't give any more propriate address.
Created attachment 49769 [details] t1_pao_dist.uns
Created attachment 49770 [details] t2_pao_dist.uns
Could anyone that understand this recap it please? How do I reproduce it?
unique stack trace btw.
Created attachment 50304 [details] stack trace I received trying to reload a pdf file multiple times this is a stacktrace I received trying to reproduce the bug. I simply tried reloading the pdf file from bug 311154 multiple times and evince crashed. The stack trace looks different, but I thought it may be relevant.
if this is on the blocker list, then it should be set NEW.
I need a clear explanation of how to reproduce this.
for the record: no crash here with Evince 0.1.9
Confirming with Evince 0.4.0 Open the file and re-read it several times with the reload button.
+ Trace 64595
This problem should be really fixed in CVS. Hope, there will be a release with fix included. *** This bug has been marked as a duplicate of 314986 ***
seems to be fixed