Closed
Bug 375326
Opened 18 years ago
Closed 16 years ago
JVM doesn't exit if a content policy is installed
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jwkbugzilla, Unassigned)
References
Details
Attachments
(2 files)
I am pretty sure this has been reported before but I think that bug was resolved (I could not find it amongst the open bugs). If a content policy implemented in JavaScript is installed JVM will not terminate properly - Firefox doesn't exit. Tested with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070325 Minefield/3.0a3pre and JRE 1.6.0-b105 (latest version at the moment). I see the same effect in Firefox 2.0.0.3 but that's probably an entirely different issue. Steps to reproduce:
1. Copy TestPolicy.js (minimal content policy, next attachment) into the components directory of your Firefox.
2. Create a file named .autoreg in your profile and restart Firefox.
3. Open testcase (only contains an <applet> tag for an applet that doesn't exist).
4. Press Alt+F4 to exit Firefox.
If you now open the list of processes you will see that Firefox didn't terminate.
|
Reporter | |
Comment 1•18 years ago
|
||
|
|
Reporter | |
Comment 2•16 years ago
|
||
WORKSFORME in Firefox 3.0.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
|
||
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•