Closed Bug 274597 Opened 20 years ago Closed 19 years ago

overflow: auto on tbody tag crashes browser

Categories

(Firefox :: General, defect)

Sun
Solaris
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: ekbustad, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

Browser crashed immediately when it tried to render this page.
Removing the "overflow: auto" enabled page to be rendered.
The presence of actual <tbody> tags in the table does make any
difference, but the presence of a <table> does.  The following 
messages are written to the terminal when the crash occurs:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  12 (X_ConfigureWindow)
  Value in failed request:  0x0
  Serial number of failed request:  33707
  Current serial number in output stream:  33715
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  12 (X_ConfigureWindow)
  Value in failed request:  0x0
  Serial number of failed request:  33708
  Current serial number in output stream:  33716

This version of Firefox is:
Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.5) Gecko/20041110 Firefox/1.0
This version is unoffically blessed for use here -- I will probably not be
able to load a newer one for a while.

Note: Netscape 7.0 on the same platform crashes on this same page,
but w/o any message written to the terminal.

This page was cut down to the minimum necessary to show the problem,
the original page contained a second, *much* larger table that the
"overflow: auto" style was intended to apply to.
Severity: normal → critical
Keywords: crash
WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041214
Firefox/1.0+
Works on my iBook, also.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.