Closed Bug 155354 Opened 23 years ago Closed 23 years ago

Opening the page www.vr.fi/keskustelu/inter.htm will jam or crash mozilla.

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hingo, Assigned: Matti)

References

(
URL
)

Details

... at least most of the time. I'm not sure whether this is a problem in showing the page or something happening with the network transfer. I'll attach a recent copy of the page too.
wow, what a fascist policy on attachment size! Ok, here is a copy of the page: http://www.hut.fi/~hingo/tmp/mozillabugs%20-%20Inter%20rail%20-keskustelu.htm
Again, my exact build is Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
WFM on Mozilla 1.0 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 and yesterday's 20020701 Trunk build for windows.
wfm with win2k build 20020630..
with linux build 20020701, Mozilla appeared did appear to hang duing page load. I fired up debug build to get a stacktrace and it did freeze for a bit, but eventually rendered the page ok. Binary build took > 2 minutes to load. Henrik: if you wait long enough, does the page eventually load?
In fact, yes it did. Approx 20 secs when loading from hard disk. (I could have sworn I waited at least that long yesterday.) I guess when you add a random network hiccup to that, it makes it look like nothing is happening. I also tried at work, same 1.0 build on win2000, and it also worked. So, false alarm, calm down. Whether you want to tune something based on this or just forget it is up to you.
... oh, but now that I think of it, once it actually crashed all browser windows. That one I haven't been able to repeat.
did you get a talkback ID for the crash?
No, everything just disappeared.
WFM - Trunk build 2002081304 - WinXP.
This is oviously a VERY long page, and I suspect that layout is doing incremental reflows much too often for the amount of data on the page, and because layout is not interruptable, the UI stops responding (See Bug 51202, Bug 67752)... the crash was probably caused by an out-of-memory condition or some similar anomaly. I am going to mark this bug WONTFIX because there are already bugs files on the underlying issues. If you continue to crash on this page and can provide a talkback ID or a stacktrace, feel free to re-open this bug... perhaps there is another problem lurking that can be fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.