Closed Bug 35762 Opened 25 years ago Closed 25 years ago

crashes browser (freeze) (M14 up to latest build)

Categories

(SeaMonkey :: General, defect, P3)

x86
All
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: wwsmurf, Assigned: asa)

References

()

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m14) BuildID: 2000041308 Reproducible: Always Steps to Reproduce: 1.try loading the URL 2. 3.
Can't reproduce this with Build 2000041309 on Linux. Also, the provided URL does not exist.
*** Bug 35766 has been marked as a duplicate of this bug. ***
cannot reproduce this with 041308 build under NT. The URL redirects to hemestead.com which works fine. Reporter I'm resolving this worksforme. If you can point us to the URL that causes the problem then please take a look at the bg writing guidelines and reopen this bug with more information. Thanks. The bug writing guidelines can be found at http://www.mozilla.org/quality/bug- writing-guidelines.html
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
wfm also under win98, verifying
Status: RESOLVED → VERIFIED
This doesn't crash me under NT but it does freeze the browser. Tested with 041409 build. Anyone see anything ugly in that HTML? Reopening and updating URL field.
Status: VERIFIED → UNCONFIRMED
Resolution: WORKSFORME → ---
does not crash browser anymore html for this page suxx, displays blank
m14 and 2000-03-29 also freeze. m13 says "Error loading page...". Extending summary.
Summary: crashes browser (latest build) → crashes browser (freeze) (M14 up to latest build)
Confirming bug, setting OS to all (I run PC/Linux, Mac is untested yet), and severity to critical. I didn't manage to save the complete page locally. Neither wget nor the Netscape composer can do this: a recursive wget returns a 404 error, and the Composer isn't very helpful because the site does extensive sniffing and says it can't deal with JavaScript. Setting network.http.version to "1.0" does not help either. Don't know how to track this down.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
Well, actually, the page loads successfully, if you are patient enough: Document http://www.homestead.com/breakdancingheavan/bdh.html loaded successfully Document: Done (258.016 secs) If I use our cache proxy, the second time I load the page it's even quite fast: Document http://www.homestead.com/breakdancingheavan/bdh.html loaded successfully Document: Done (35.518 secs) It still freezes for some long intervals while loading (20 secs up to 2 minutes), but finally it even handles stop requests if you are patient enough. The page doesn't display as intended, but probably that's some other bug (redirections, javascript,...). So I'd like to unconfirm this bug again, but since that's not possible, I am only going to lower the severity back to normal. Sorry for the confirmation. I won't touch this bug again... Maybe the scheduling/event-handling people are interested in this bug as a testcase.
Severity: critical → normal
Adding crash keyword.
Keywords: crash
elig, can you help us out on this one. I'm stumped.
request for resolved fixed status . . . has been working for some time. . .
Hi, Asa --- I don't know what to suggest; this works for me using the 4.26.00 Mozilla build on Mac OS & Win32. (e.g. http://www.homestead.com/breakdancingheavan/bdh.html displays within 5 seconds.)
thanks elig, reporter says it's good now. Marking WORKSFORME.
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → WORKSFORME
Verified with 050808 build under NT.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.