248900 - browser crash BadShmSeg Major opcode Minor opcode Segment id Serial number failed request

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Kasi Viswanadham Vallabhaneni]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040218
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040218

Gtk-WARNING **: invalid cast from `GtkSuperWin' to `GtkWidget'
X Error of failed request:  BadShmSeg  (invalid shared segment parameter)
  Major opcode of failed request:  131 (MIT-SHM)
  Minor opcode of failed request:  2 (X_ShmDetach)
  Segment id in failed request:  0x1
  Serial number of failed request:  145
  Current serial number in output stream:  189



Reproducible: Always
Steps to Reproduce:
1.open the webbrowser 
2.go to http://mail.yahoo.com , click on inbox , than it will crashes
3.

Actual Results:  
the browser will crash with the followin information
Gtk-WARNING **: invalid cast from `GtkSuperWin' to `GtkWidget'
X Error of failed request:  BadShmSeg  (invalid shared segment parameter)
  Major opcode of failed request:  131 (MIT-SHM)
  Minor opcode of failed request:  2 (X_ShmDetach)
  Segment id in failed request:  0x1
  Serial number of failed request:  145
  Current serial number in output stream:  189



Expected Results:  
I should see my inbox of yahoo mail

The problem is not only facing by me , Here other users also facing the problem.
suddenly it crashes without any reason.

Comment 1

[Olivier Cahagne]

see 224427 for the warning, either yours is worse since you crash or the crash
in not related to the warning, not sure.

Comment 2

[Haggai Eran]

Hi
I'm experiencing the same problem.
Some sites cause the browser to crash.
I'm using firefox 0.9.3 on debian sid.

I get this output before it closes:
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 28 error_code 172 request_code 149 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 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.