Bug Tracker

Modify

Ticket #9895 (closed bug: worksforme)

Opened 3 years ago

Last modified 2 years ago

Memory Leak in fxqueue

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

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

comment:1 Changed 3 years ago by john

  • Priority changed from undecided to blocker
  • Component changed from unfiled to effects
  • Milestone changed from None to 1.7

comment:2 Changed 3 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 3 years ago by rwaldron

  • Status changed from new to open

comment:4 Changed 3 years ago by john

  • Owner set to dmethvin
  • Status changed from open to assigned

comment:5 Changed 3 years ago by dmethvin

  • Status changed from assigned to closed
  • Resolution set to worksforme

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 3 years ago by dmethvin

  • Milestone 1.7 deleted

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.