Closed
Bug 190005
Opened 23 years ago
Closed 23 years ago
browser hardlocks/segfaults when scrolling on W3C Validator Page
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 173204
People
(Reporter: brad, Assigned: blizzard)
References
()
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202
Operating System: RedHat 8.0 Psyche (2.4.18-19.8.0) athlon with all the latest
updates
Attempting to scroll to the code section on
http://validator.w3.org/check?uri=http%3A%2F%2Fstartup.getcoded.net%2F (which
appears to be vaild XHTML 1.0 Strict, LMAO) results in a hardlock/segfault using
either the scrollbar (on right side), scrolling arrows or scroll wheel.
Reproduced on three RH8.0 machines and a windows machine (no segfault).
Mozilla version:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202, build 2002120219
Reproducible: Always
Steps to Reproduce:
1. Open Mozilla
2. Browse to http://validator.w3.org/check?uri=http%3A%2F%2Fstartup.getcoded.net%2F
3. Scroll past the code section or even browse to
http://validator.w3.org/check?uri=http%3A%2F%2Fstartup.getcoded.net%2F#line-65
Actual Results:
Hardlock/segfault. Program can only be closed by a ps -auxf and a killall
mozilla-bin
Expected Results:
Uh... Mozilla should scroll down like I asked it to, IMHO ;)
Machine 1 uses Mozilla 1.2.1 XFT for RH 8.0 with Modern theme. Machine 2 uses
Galeon 1.2.7 with mozilla 1.2.1 XFT for RH8. Machine 3 is essentially a clone
of Machine 2 (Mozilla 1.2.1 XFT for RH 8 - Modern Theme). All Machines
segfaulted upon scrolling (slow or fast, sporadic, etc)
| Reporter | ||
Comment 1•23 years ago
|
||
| Assignee | ||
Comment 3•23 years ago
|
||
Looks like a dup of
*** This bug has been marked as a duplicate of 173204 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•