Closed Bug 337405 Opened 20 years ago Closed 20 years ago

Viewing entries from Movabletype 3.2 leaks

Categories

(Firefox :: General, defect)

1.5.0.x Branch
x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 241518

People

(Reporter: Usul, Unassigned)

References

()

Details

(Keywords: memory-leak)

This happens When I'm logged in my MT 3.2 install. On the main page I'm able to see all blogs being published from this installation. Clicking on the entries link for one weblog triggers dbaron's leak detector extension : The following JavaScript objects from a window that was recently closed are still held by native code. [leaked object] <above url> 22 22 function (evt) { resturn self.click(evt):} prototype [object Object]
This sounds like bug 241518. Can you retest with a trunk build of Firefox?
(In reply to comment #1) > This sounds like bug 241518. Can you retest with a trunk build of Firefox? > Will Do.
this is fixed on trunk. based on comment #1 closing as duplicate. *** This bug has been marked as a duplicate of 241518 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
addendum: FF 1.5.0.5: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 plus a bunch of extensions I also misstated the initial memory usage. Right now, with a fresh session having open five tabs on mozilla.org, I use some 45 megs, not 100 megs.
You need to log in before you can comment on or make changes to this bug.