Loading above page crashes browser

RESOLVED WORKSFORME

Status

()

Firefox
General
--
critical
RESOLVED WORKSFORME
12 years ago
11 years ago

People

(Reporter: cypherpunks, Unassigned)

Tracking

({crash})

2.0 Branch
x86
Linux
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 07/14, URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

Loading http://framboise78.free.fr/Paris.htm crashes my browser with the following error: 
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 25884 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.)

It happens in normal mode, and in safe mode. System has huge amounts of resources (>1GB RAM, mostly free. Other than Firefox, only a few xterms, emacs, and one <20MB application were running). ATI Radeon Mobility 9700 graphics card, with 128MB RAM, and proprietary ATI driver. 

There is a number of similar bugs in the bug database, some of which date back to older Firefox versions. I do not know if they are the same bug or not. 

Reproducible: Always

Steps to Reproduce:
1. Go to http://framboise78.free.fr/Paris.htm
Actual Results:  
Firefox crashes, with: 
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 12722 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.)


Expected Results:  
Pretty web page. 

System is Debian GNU/Linux 3.1. Firefox is official build from Mozilla.org. System is a high-end machine, doing almost nothing at the time, so this was not a simple resource shortage. 

Given that Firefox crashes, it is an important bug, since many crashes can be exploited as e.g. buffer overflows.
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Keywords: crash
Whiteboard: CLOSEME 07/14
Version: unspecified → 2.0 Branch

Comment 2

11 years ago
WFM with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 on Debian Etch+~Lenny
$ free
             total       used       free     shared    buffers     cached
Mem:       1036644     992252      44392          0      22088     401960
-/+ buffers/cache:     568204     468440
Swap:      1566296     394848    1171448

Comment 3

11 years ago
No response → resolving WORKSFORME.
If you see this bug with latest versions, feel free to reopen. Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.