Mozilla 1.7 may crash at random on random on SunRay systems.



15 years ago
14 years ago


(Reporter: ragge, Unassigned)




Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030911
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040628

After being running for some time, between a few hours up to a few days,
Mozilla just terminates with the following X error:

X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  255 ()
  Minor opcode of failed request:  0
  Serial number of failed request:  640470
  Current serial number in output stream:  640474

Major/minor opcodes are always 255/0, but the other numbers may vary.
Also notable is that it's only some people for which mozilla crashes,
other people do never get a crash even though the read web pager are 
about the same.  All people are using the same Sunray server.

The crashes also happens with 1.6 and 1.5, but older versions seems to survive.

The only used plugin is flashplayer.

Reproducible: Always
Steps to Reproduce:

I have no clues about what additional information you may want, but feel free 
to ask me to try different stuff.

Comment 1

15 years ago
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a3) Gecko/20040726

I have this not often any more with new version of mozilla and
with gtk 2.4.3


15 years ago
OS: SunOS → Solaris


15 years ago
Keywords: crash
Product: Browser → Seamonkey
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.