Skip to main content

Bug Tracker

Side navigation

#9895 closed bug (worksforme)

Opened July 22, 2011 07:57PM UTC

Closed September 09, 2011 02:25PM UTC

Last modified March 14, 2012 04:20AM UTC

Memory Leak in fxqueue

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

Sounds like we're not clearing up the queue later on? Either way, sounds bad.

Attachments (0)
Change History (6)

Changed July 22, 2011 07:58PM UTC by john comment:1

component: unfiledeffects
milestone: None1.7
priority: undecidedblocker

Changed July 23, 2011 01:40PM UTC by dmethvin comment:2

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.

Changed July 25, 2011 04:20PM UTC by rwaldron comment:3

status: newopen

Changed July 25, 2011 04:30PM UTC by john comment:4

owner: → dmethvin
status: openassigned

Changed September 09, 2011 02:25PM UTC by dmethvin comment:5

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.

Changed September 27, 2011 04:04AM UTC by dmethvin comment:6

milestone: 1.7