Closed Bug 175465 Opened 22 years ago Closed 22 years ago

EMBED tag with AUTOSTART wav file causes browser to hang and consume all CPU and memory

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 157554

People

(Reporter: superdotfly, Assigned: peterl-bugs)

Details

(Keywords: hang) 

Open the following document:
<HTML><BODY><EMBED SRC="test.wav" AUTOSTART=TRUE></BODY></HTML>
(Important: put a wave file named "test.wav" in same directory as this document.)
Result: browser hangs with 100% CPU utilization, and memory usage ramps up at an
alarming rate.  Process has to be euthanized before consuming all available memory.
Correction/clarification:
The previouly mentioned test would have to be done on a browser which had never
installed a plugin to handle wav files, and in a situation in which
"plugins.netscape.com" could not be reached (e.g. offline).  To reproduce this
behavior more generally, use a fake filename extention for which no plugin has
been installed, e.g.:
<HTML><BODY><EMBED SRC="test.asdf" AUTOSTART=TRUE></BODY></HTML>
and load it in the browser with "plugins.netscape.com" unreachable (e.g. add a
bogus entry to WINNT\system32\drivers\etc\hosts before launching browser).
The bug appears to be triggered by failing to contact "plugins.netscape.com"
while trying to get a new plugin.
-> plugins

be sure that there is no error dialog in the background
Assignee: asa → beppe
Severity: normal → critical
Component: Browser-General → Plug-ins
Keywords: hang
QA Contact: asa → shrir
what plug-in do you have mapped to .wav files? What version of that plug-in are
you using? What version of the browser are you using?
Regarding which plugin is mapped to wav files, please read additional comment #1
--- this is not specific to wav files.  Recommend testing with a bogus novel
filename extension that always forces an attempted plugin download as explained
there.
This was using Phoenix version 0.3

I cannot reproduce this using a current build from the trunk. I have tried bogus
extensions and no extensions as well. Do you have a particular site that you
have gone to that produced this problem?
I don't hang but I don't get the default plugin either on:
<HTML><BODY><EMBED SRC="test.asdf" AUTOSTART=TRUE></BODY></HTML>
(with TYPE=anything I see it, but no hang) 

I think not seeing the default plugin in this case is another bug. The problem
is that we don't handle initial stream failures very nicely. Looking in the
debugger, we simply return error because the file is not found in
|nsPluginStreamListenerPeer::OnStartRequest| instead of showing the default
plugin or trying alternate content. This problem is described in bug 157554.
reporter: please clarify is this mozilla bug or phoenix one?
reassign
Assignee: beppe → peterl
Also try updating Quicktime which handles WAV files to stop hanging.

*** This bug has been marked as a duplicate of 157554 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.