383967 - crash after while when logged in mail, same in the safe mode

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Jirik]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.8.1.4) Gecko/20060601 Firefox/2.0.0.4 (Ubuntu-edgy)
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.8.1.4) Gecko/20060601 Firefox/2.0.0.4 (Ubuntu-edgy)

opening the mail window mozilla crashes after while reporting:
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadShmSeg (invalid shared segment parameter)'.
  (Details: serial 206 error_code 165 request_code 143 minor_code 2)
  ...
same in the safe-mode run

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Firefox doesn't have a "mail window". Do you mean that loading a webmail application causes a crash?

Comment 2

[Jirik]

(In reply to comment #1)

yes, logged in mail, trying to read one accidentaly crashes. but maybe it is more connected with the webpage, becouse I tried to run firefox in the safe mode and also used Epiphany wiever for the same task wiever all crashed same way

Comment 3

[Jirik]

sorry for the wiever - means viewer

Comment 4

[Adam Guthrie]

If you open up a terminal, run `export XLIB_SKIP_ARGB_VISUALS=1' then run Firefox by typing `firefox' do you still crash?

Comment 5

[Jirik]

yes, still crashes. the full report in terminal is:
...
open dsp: Device or resource busy
open dsp: Device or resource busy
open dsp: Device or resource busy
open dsp: Device or resource busy
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadShmSeg (invalid shared segment parameter)'.
  (Details: serial 262 error_code 165 request_code 143 minor_code 2)
  (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 6

[Wayne Mery (:wsmwk)]

do you still see this problem using FF 3.5 beta**, or latest update of FF 3.0 started in safe mode***?

If yes, please comment
If not, please close with resolution set to WORKSFORME. Or INVALID (if problem was extension or the like)

** http://www.mozilla.com/en-US/firefox/all-beta.html
*** http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 7

[u88484]

This bug was reported using a version of Firefox that security and stability updates are no longer provided for.  All users are strongly encouraged to upgrade to Firefox 3 by selecting 'Check for Updates' in the Help menu or by going to http://www.mozilla.com/en-US/firefox/firefox.html

If you can no longer reproduce this bug using the latest Firefox 3.0.x version, please change the status of this bug to 'RESOLVED' 'WORKSFORME'.

If you can still reproduce this bug, please provide additional details to help resolve this issue.