479779 - after a crash, firefox 3.1b2 always fails at startup

Status: RESOLVED DUPLICATE of bug 462668

(Firefox :: General, defect)

Description

[Michele]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.5 (like Gecko)
Build Identifier: 3.1b2

This is the error I'm getting:

firefox --sync
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2863 error_code 11 request_code 53 minor_code 0)
  (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.)



The problem started to occur after a crash while using the zoom function in google maps.

Reproducible: Always

Steps to Reproduce:
1. Open Google maps
2. 'Play' with the zoom 
3.
Actual Results:  
Firefox does not launch any more. I have deleted the 'firefox' folder in ~/.mozilla and I got this error:

firefox
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 2194 error_code 179 request_code 153 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.)


If launched with the --sync option:
firefox --sync
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 3690 error_code 11 request_code 53 minor_code 0)
  (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.

Comment 1

[Matthias Versen [:Matti]]

doesn't block development.
Is this still an issue with FF3.1b3 ?