164547 - hang 100% cpu usage with very high priority, everything stops responding, Flash player/plugins NOT installed.

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[wantoseetheworld]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530

hang 100% cpu usage with high priority, (even mouse cursor stops responding, 
but music still play in background so not completely crashed) Flash 
player/plugins NOT installed this time. This happens randomly when displaying 
any page by browsing the web in general, not specific to any applications 
running along Mozilla, all the latest builds did it at least once, but I didn't 
try the latest nighty builds.

Reproducible: Sometimes

Steps to Reproduce:
1.Browsing the web in general..?!?
2.
3.

Actual Results:  
hang 100% cpu usage with high priority, (even mouse cursor stops responding, 
but music still play in background so not completely crashed)

Expected Results:  
simply display some Web pages.

Applied the modern theme that comes with Mozilla, no other theme installed
Did it with 1.0, 1.1 Alpha, event 1.1 beta (but im not suse 100% with the beta)
No plugins installed, not even flash, (but the web page may contain flash that 
is displayed by a missing plugin).
No real crash, simply the system is not responding, but the status never ends.
MP3 player still play (I guess higher priority).
At the time of writing this, I notice that flash content does play correcly, 
but I never installed any plugin... Automated instalation?

Comment 1

[Wesha]

Reporter: are you using HTTP/1.1 pipelining ? (see Preferences -> Advanced ->
HTTP Networking). If you are, it's bug 153772

Comment 2

[Benjamin Smedberg]

Marking WORKSFORME... [e-mail]:  per comment #1, do you have
HTTP pipelining enabled (Edit/Preferences/Advanced/HTTP Netorking)?  The HTTP
pipelining issue was fixed on 2002-07-26: please try a newer build to see if
this fixes the problem.

If you still experience this problem using a newer build such as 1.2a or one of
the daily builds, please re-open this bug.  Do you happen to have a debugger (MS
Visual Studio or one of the simpler MS debuggers) installed on your system?