Closed Bug 481236 Opened 15 years ago Closed 13 years ago

X Window System error on certain sites: 'BadValue (integer parameter out of range for operation)'

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
3.5 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: cjsthompson, Unassigned)

References

(
URL
)

Details

(Whiteboard: [CLOSEME 2011-2-25]) 

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090303 Shiretoko/3.1b3pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090303 Shiretoko/3.1b3pre

Firefox crashes on http://haiku-os.org.

Reproducible: Always

Steps to Reproduce:
1. Load http://haiku-os.org


Actual Results:  
Crash

Expected Results:  
Loaded the site.
Works fine for me. (3.1b3pre on Linux)

When reporting a crash, please post crash ID:
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
I'm sorry but I can't post a crash ID because the mozilla crash reporter doesn't work for me. It requires GConf, which requires bonobo and other deprecated/useless stuff which I'm not about to install on my machine.

However I tried running gdb like this:

"./run-mozilla.sh -g -d gdb ./firefox-bin"

But there are no symbols so it's useless.

I have tried loading haiku-os.org in safe mode and here is what I got:

$ firefox -safe-mode
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 34961 error_code 2 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.)
Another hint: it doesn't crash with Minefiled build 20081009 which I'm using on another machine.
X error; not a crash.

In the future, you usually shouldn't file 3 different reports for this. If you're crashing at a lot of sites chances are it's the same cause. Best to just file one bug report and troubleshoot then spin-off others if they really are separate.
Summary: Firefox crashes on http://haiku-os.org → X Window System error on certain sites: 'BadValue (integer parameter out of range for operation)'
Version: unspecified → 3.1 Branch
Ok, sorry for this. I thought it would be useful to narrow down what these page had in common.
What is your distro and X version? (run "X -version" from terminal to check X)
For what it's worth, I'm on Kubuntu 8.04 w/ X.Org X Server 1.4.0.90.
My distro: Slackware 12.2
DE: Xfce 4.6.0

$ X -version

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux blabl 2.6.29-rc6-blabl-5 #2 Sun Mar 1 18:34:07 CET 2009 i686
Build Date: 30 June 2008  11:35:29PM

Gtk+ 2.14.7
Pango 1.22.4
Atk 1.24.0
Glib 2.18.4

---

I've had these same crashes also with Slackware 12.1 before upgrading but I just kept using the Minefield build that works and trying a new build every week or so to see if the problem had been fixed.
See if you can narrow down the trigger. Try disabling images (under preferences, content) and see if you still get the error. If that fixes it, try viewing the source and loading up the images on the page one by one until you find the culprit. (recent versions have auto-linkification in view-source, so you'll just need to click the links; hit backspace to go back) If we can find a minimized cause here we can investigate better.
Disabling images fixes it. However the faulty image is not in the HTML file    
because I then re-enabled images, and disabled javascript and it doesn't crash 
either. So the the 'bad' image must be loaded from one of the external .js
files. It's getting late so I will continue to investigate that tomorrow as 
there's 9 external .js files to look throughout.
You could just try one of the other 2 sites instead of digging through that. ;)
Disabling images and/or JavaScript on http://behindkde.org/people/seli/ does not fix the issue.
Allostreaming does not crash anymore this morning. Maybe the 'bad' image there was one of their ads.
On haiku-os.org I can't reproduce today what happened yesterday. So it must be in the ads too.
Now haiku-os.org crashes again... I think I should try upgrading X.org...
Ok, you won't hear for me for a few days because I have to go somewhere. I'm taking my laptop with me and I'll be compiling X.org to see if this fixes anything.
So, finally I got time to upgrade X.org manually to the latest stuff (X server 1.6.1, xf86-video-ati 6.12.2 etc... I upgraded Firefox to a recent build of 3.5b5 and still the problems persist.
Re-compiled cairo, pango and Gtk+ to the latest stuff and added the debian diff fixes to all that. Still it crashes. I ran firefox with --sync.

wotan ~ $ firefox --sync
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 33168 error_code 2 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 program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 33169 error_code 4 request_code 54 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.)
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.