Ticket #7383 (closed bug: fixed)

Opened 2 years ago

Last modified 22 months ago

Possible Memory Leak When Repeatedly Creating and Destroying Tabs

Reported by: nogwater Owned by:
Priority: minor Milestone: 1.9.0
Component: ui.tabs Version: 1.8.12
Keywords: Cc:
Blocking: Blocked by:

Description

jsFiddle version:  http://jsfiddle.net/YgLFt/3/ Simple sample at:  http://www.apejet.org/aaron/code/tabs_test/

The page uses the demo tabs from the documentation. My test code calls .tabs("destroy") and .tabs() to remove and re-create the tabs 100 times per run.

IE 7 is showing about 10 MB of memory growth per run according to the task manager. Firefox 3.6 also shows memory growth, but less consistently. Using the web inspector in Chrome 12, the heap shows growth (not a lot, but some) if I take a snapshot, run the test, run the garbage collector, and take another snapshot. As far as I can tell, the jQuery.cache isn't growing between runs.

Change History

comment:1 Changed 22 months ago by scott.gonzalez

  • Status changed from new to closed
  • Resolution set to fixed

I've confirmed that this is fixed in master using Chrome's heap profiler.

Note: See TracTickets for help on using tickets.