Closed
Bug 246509
Opened 20 years ago
Closed 19 years ago
Crash when loading page at tylock.com
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: alex, Assigned: bugzilla)
References
()
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040612 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040612 Firefox/0.8.0+ Loading this page crashes Firefox immediately. Reproducible: Always Steps to Reproduce: 1. Load http://www.tylock.com/procedure_pgs/customLASIK.html Actual Results: Crash Expected Results: No crash :). I would have included talkback info, but it appears that talkback isn't included in the nightly Firefox zip builds.
Comment 1•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040609 Firefox/0.8.0+ (FF0.9rc) WFM, only loads slow
Reporter | ||
Comment 2•20 years ago
|
||
I did some further testing to determine which win32 builds had this bug. Builds up to and including 2004-06-01-09 are ok, but builds starting with 2004-06-02-09 crash. I also discovered that if the page is in your cache, Firefox doesn't crash. So, if you're expecting a crash but it isn't happening, try clearing your cache and loading the page again.
Reporter | ||
Comment 3•20 years ago
|
||
(In reply to comment #1) > Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040609 > Firefox/0.8.0+ (FF0.9rc) > WFM, only loads slow Peter: Are you using the branch? This may only be on the trunk.
Comment 4•20 years ago
|
||
Yes, that's why I added the comment, i am using branch
Comment 5•19 years ago
|
||
FWIW, WFM under Mac OS 10.3.8, Firefox PPC 7450 optimized build (Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+). This is a trunk build. No problems.
Reporter | ||
Comment 6•19 years ago
|
||
Yup, this page works fine now :-/. -> WFM.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•