Closed Bug 323405 Opened 20 years ago Closed 18 years ago

Memory leak when reorganizing bookmarks

Categories

(Core :: General, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bernard.alleysson, Unassigned)

References

Details

(Keywords: memory-leak)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060113 Firefox/1.6a1 Leaked inner window 21d8de0 (outer 216da48) at address 21d8de0. ... with URI "chrome://browser/content/bookmarks/bookmarksManager.xul". Leaked outer window 1a20008 at address 1a20008. Leaked outer window 216da48 at address 216da48. Summary: Leaked 3 out of 8 DOM Windows Leaked 0 out of 26 documents Leaked 0 out of 4 docshells Step: 1 - Open bookmark manager 2 - Move up one bookmark in any bookmark folder Results: from leak-gauge.pl: Leaked inner window 21d8de0 (outer 216da48) at address 21d8de0. ... with URI "chrome://browser/content/bookmarks/bookmarksManager.xul". Leaked outer window 1a20008 at address 1a20008. Leaked outer window 216da48 at address 216da48. Summary: Leaked 3 out of 8 DOM Windows Leaked 0 out of 26 documents Leaked 0 out of 4 docshells
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060114 Firefox/1.6a1 ID:2006011405 I see this too. Related to bug 168411 mayhap?
confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bug #324461 (linux) may be a duplicate of this
*** Bug 324461 has been marked as a duplicate of this bug. ***
I can reproduce with SeaMonkey trunk build 2006011909. It can also be repdroduce on Linux.
Component: Bookmarks → XP Miscellany
OS: Windows 2000 → All
Product: Firefox → Core
QA Contact: bookmarks → brendan
Is this still a problem with places on trunk? If not, this probably should be closed.
I can't reproduce with Firefox 3 beta 1. Closing as WFM. Please comment if you can still reproduce.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Component: XP Miscellany → General
QA Contact: brendan → general
You need to log in before you can comment on or make changes to this bug.