Ticket #1122 (closed defect: fixed)

Opened 2 years ago

Last modified 16 months ago

Memory Leak In tabContainer

Reported by: prashanth.shivakumar@… Owned by: peller
Priority: high Milestone: 0.9
Component: Dijit Version: 0.3
Severity: normal Keywords:
Cc:

Description

http://download.dojotoolkit.org/release-0.3.1/dojo-0.3.1-ajax/demos/widget/tabContainer.html

On hitting above URL Increases memory in IE on reloading/refreshing.. Also in our application when we open/close tabs dynamically it increases memory in IE which causes our application to freeze[because of memory leak]

Change History

Changed 2 years ago by dylan

  • milestone set to 0.5

Changed 2 years ago by guest

  • milestone changed from 0.5 to 0.4

Changed 2 years ago by guest

Hi, can you please reschedule this issue to 0.4 because it makes our web application useless after opening about a particular browser child window (with a tabcontainer in it) about 30 times.

Changed 2 years ago by bill

Testing against latest now, refreshing tests/widget/test_TabContainer.html doesn't increase memory usage. However, drip shows some problems.

Also tested against tests/widget/test_LayoutCode.html; hitting the "Tab Layout" button, to create a tab widget, then the "destroy" button (to remove said wiget), and then repeating, causes some leaked memory (10 times causes 3M leak).

Changed 2 years ago by bill

  • milestone changed from 0.4 to 0.4.1

Changed 2 years ago by bill

  • milestone changed from 0.4.1 to 0.5

Changed 21 months ago by koranteng

  • owner changed from bill to koranteng

Changed 18 months ago by peller

  • component changed from Widgets to Dijit

Changed 16 months ago by bill

  • owner changed from koranteng to peller
  • milestone changed from 0.9 to 1.0

Changed 16 months ago by bill

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from 1.0 to 0.9

Just tried refreshing

http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/layout/test_TabContainer.html

against IE6 30 times. Minimal memory increase (about 2M).

Note: See TracTickets for help on using tickets.