MozillaZine

[SOLVED] Crash - 'RenderBadPicture'

Discussion of bugs in Seamonkey
ultra_violence
 
Posts: 4
Joined: April 5th, 2010, 9:17 am

Post Posted April 5th, 2010, 9:26 am

Recently, I've been experiencing what seems to be a
random crash with Seamonkey (Since 2.0.3). It's been
occuring for a month or two now; I've upgraded my
system many times but nothing seems to fix it.

Running it in a terminal, it crashes out with:
Code: Select all
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 575453 error_code 167 request_code 151 minor_code 7)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


I have not found the criteria to reproduce it as of yet,
it does indeed seem to be random although it seems
to occur more frequently after I close tabs. I've gone
through the whole rigmarole with disabling plugins,
deleting my profile directory etc but no results. I sure
hope someone can figure out what's going on, the only
other browser I'd use is links!

I've posted this over on the Arch Linux forums as well;
http://bbs.archlinux.org/viewtopic.php?id=93650
Seems many other users with different setups are
having the same problem...

My system:
Arch Linux 32bit
Kernel 2.6.32
e17 (From SVN)
Seamonkey 2.0.4
nVidia proprietary driver
Latest stable xorg server
Latest GTK etc.

Thank you in advance for any insights or remedies.
Last edited by ultra_violence on April 23rd, 2010, 3:01 am, edited 1 time in total.

therube

User avatar
 
Posts: 18481
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted April 5th, 2010, 4:22 pm

Do you get a (SeaMonkey) crash report & have you submitted it?
about:crashes

? Bug 500105 - top crash [@ GraphWalker::DoWalk(nsDeque&)]

Last post might be hinting at a memory problem, Memtest86+?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

ultra_violence
 
Posts: 4
Joined: April 5th, 2010, 9:17 am

Post Posted April 5th, 2010, 5:05 pm

There is no SeaMonkey crash report unfortunately. I'm using the
stable branch from the Arch repos which doesn't have the QA
functionality built in so far as I know.

E17 pops up an error report with no information, only stating that
SeaMonkey returned with an error. It usually happens after closing
tabs but also more frequently when closing the browser outright.

I run memtest once a month and I have done so again today; my
RAM is perfectly healthy. It's just SeaMonkey that crashes, my
system doesn't lock up as the person said in the last post in that
link. All I can provide is the output from the terminal. I will provide
a more lengthy log next time and I will continue to see if I can
reproduce the crash.

Is there anything more I can do which might help diagnose the
problem? It's killing me to have my favourite browser crash out
on me like this.

ultra_violence
 
Posts: 4
Joined: April 5th, 2010, 9:17 am

Post Posted April 15th, 2010, 12:26 am

I still can't seem to get reproduction criteria. The browser
doesn't crash consistently on the same pages. It happens
on all of my machines now also, not just running Arch Linux.

Guess I'll just have to use chromium until this gets fixed.

Thanks for the feedback nonetheless, therube.

Andy Boze

User avatar
 
Posts: 2755
Joined: June 30th, 2005, 9:53 pm
Location: South Bend, IN

Post Posted April 15th, 2010, 2:17 pm

From what I read at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551852, it appears to be a problem with libcairo2, at least on Debian-based systems. Perhaps similar for Arch.
But then again, I may be wrong.

ultra_violence
 
Posts: 4
Joined: April 5th, 2010, 9:17 am

Post Posted April 23rd, 2010, 3:00 am

Andy Boze wrote:From what I read at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551852, it appears to be a problem with libcairo2, at least on Debian-based systems. Perhaps similar for Arch.


You were right on the mark Andy. The bug was submitted to the tracker on Arch recently. Seems the
version of libcairo2 in the Arch repos is broken:

http://bugs.archlinux.org/task/19005

I should have known better. Seamonkey couldn't possibly be broken!

Thanks all for the feedback and insights!

arifsaha
 
Posts: 14
Joined: January 19th, 2005, 8:33 pm
Location: Edmonton, AB

Post Posted October 6th, 2010, 9:46 am


Return to SeaMonkey Bugs


Who is online

Users browsing this forum: No registered users and 1 guest

cron