Bug Tracker

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#9895 closed bug (worksforme)

Memory Leak in fxqueue

Reported by: john Owned by: dmethvin
Priority: blocker Milestone:
Component: effects Version: 1.6.2
Keywords: Cc:
Blocked by: Blocking:

Description

Sounds like we're not clearing up the queue later on? Either way, sounds bad. https://bugzilla.mozilla.org/show_bug.cgi?id=670689

Change History (6)

comment:1 Changed 10 years ago by john

Component: unfiledeffects
Milestone: None1.7
Priority: undecidedblocker

comment:2 Changed 10 years ago by dmethvin

As far as the RegExp objects go, in 1.7 I've already changed .trigger() to avoid creating them if there are no namespaces. The jQuery Tools code is very trigger-happy. Sounds like that wasn't the main problem though.

comment:3 Changed 10 years ago by Rick Waldron

Status: newopen

comment:4 Changed 10 years ago by john

Owner: set to dmethvin
Status: openassigned

comment:5 Changed 10 years ago by dmethvin

Resolution: worksforme
Status: assignedclosed

I left the test case running in a tab in Firefox 6.0.2 for an hour while I monitored about:memory and didn't see any signs of leakage. I tried both tab-visible and tab-hidden during that time. Although memory use would spike to as high as 350MB, it would always settle back down to 179MB or so within a minute. This problem must have been fixed (intentionally or incidentally) on the Firefox side.

comment:6 Changed 10 years ago by dmethvin

Milestone: 1.7
Note: See TracTickets for help on using tickets.