Opened 11 years ago

Closed 11 years ago

#11600 closed defect (invalid)

AccordionContainer: memory leak on refreshing page

Reported by: Roberto Mosqueda Owned by:
Priority: high Milestone: tbd
Component: Dijit Version: 1.5
Keywords: memory leak Cc: David Schwartz, [email protected]…, [email protected]
Blocked By: Blocking:

Description (last modified by bill)

Testing type: Memory leaks

Widget: AccordionContainer

Short description: After refreshing the page several times the use of memory was increased and it was never free.

Steps to reproduce:

  1. Using Chrome, open the AccordionContainer page (/dijit/tests/layout/test_AccordionContainer.html)
  1. Press F5 or refresh the page several times (i.e. 10)

Actual results: the use of memory was increased

Expected results: the memory should be free

Attachments (1)

AccordionContainer_Chrome.jpg (199.0 KB) - added by Roberto Mosqueda 11 years ago.

Download all attachments as: .zip

Change History (3)

Changed 11 years ago by Roberto Mosqueda

comment:1 Changed 11 years ago by bill

Cc: [email protected] removed
Description: modified (diff)
Summary: When refreshing the Accordion Container samples, the memory reserved is not releasedAccordionContainer: memory leak on refreshing page

comment:2 Changed 11 years ago by Katie Vance

Resolution: invalid
Status: newclosed

Refreshing a page is not a valid memory leak test. Browsers may allocate new memory on a page-refresh, but eventually will either garbage collect and/or reuse the previous memory blocks. So memory may increase initially, but will eventually level out (at the browser's discretion).

Note: See TracTickets for help on using tickets.