Compartments and window objects leak when opening links in new windows with Restartless Restart 8 and SmartSearch 3.19

RESOLVED FIXED

Status

Tech Evangelism
Add-ons
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: ferongr, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
STR:

1. Install Restartless Restart 8 [1] and SmartSearch 3.19 [2]. Restart.
2. Open about:compartments. Note existing compartments.
2. Go to any website.
3. Right-click on a link an "Open Link in New Window".
4. Close the new window and its originating tab, and refresh about:compartments a few times. You should see ghost windows and zombie compartments from the website.
5. Disable Restartless Restart and refresh about:compartments.
6. The zombies and ghosts are dead.

[1] https://addons.mozilla.org/en-US/firefox/addon/restartless-restart/
[2] https://addons.mozilla.org/en-us/firefox/addon/smartsearch/
(Reporter)

Updated

5 years ago
Summary: Compartment and window object leak when opening links in new windows with Restartless Restart 8 and SmartSearch 3.19 → Compartments and window objects leak when opening links in new windows with Restartless Restart 8 and SmartSearch 3.19
(Reporter)

Comment 1

5 years ago
Forgot to mention, this is on the 2012-04-06 Nightly.
(Reporter)

Updated

5 years ago
Blocks: 700547
You need both restartless restart and smartsearch to see this leak?
(Reporter)

Comment 3

5 years ago
Yes.
Confirming the issue.  And also that disabling either addon stops the leak

erik: would you mind having a look in restartless restart to see if you can establish where the leak is coming from?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Note that bug 743215 has similar steps to reproduce (open a new window), and both add-ons are authored by the same developer, so this may be related to common code in both add-ons.
Blocks: 668871
(In reply to Jorge Villalobos [:jorgev] from comment #5)
> Note that bug 743215 has similar steps to reproduce (open a new window), and
> both add-ons are authored by the same developer, so this may be related to
> common code in both add-ons.

I just tried with a FF18 trunk build and couldn't reproduce, so I'm guessing that Firefox 15 fixes this problem, even though it didn't fix bug 743215.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.