Closed
Bug 41632
Opened 25 years ago
Closed 25 years ago
plugin leaked if page has a js error
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sean, Assigned: rogerl)
Details
(Keywords: memory-leak, testcase)
Attachments
(3 files)
If
1) you load a page that has an <embed> plugin AND
2) the page uses 'navigator.plugin' in a js block AND
3) the page experiences a js exception in any js block
then the embedded plugin does not get freed.
Not sure if this belongs to DOM or JS Engine.
Will attach test case.
| Reporter | ||
Comment 1•25 years ago
|
||
| Reporter | ||
Comment 2•25 years ago
|
||
| Reporter | ||
Comment 3•25 years ago
|
||
| Reporter | ||
Comment 4•25 years ago
|
||
The third attachment is a modified version of the npsimple plugin. You can use
the makefile in /mozilla/modules/plugin/test to build the plugin. It has
printfs for the constructor and destructor for SimplePlugin and
SimplePluginInstance classes.
View the first 2 testcase html pages after building and installing the sample
plugin. When you close the browser after viewing the first test case, you will
see that the destructor for both the Plugin and the PlugInstance are reached.
When you close the browser after viewing the second testcase, both objects are
leaked.
Keywords: testcase
| Reporter | ||
Comment 6•25 years ago
|
||
It's working ok now - don't know when it got fixed. Resolving as WORKSFORME.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•