#11599 closed defect (invalid)
Slider: memory leak on page refresh
| Reported by: | Roberto Mosqueda | Owned by: | Douglas Hays |
|---|---|---|---|
| Priority: | high | Milestone: | 1.6 |
| Component: | Dijit - Form | Version: | 1.5 |
| Keywords: | memory leak | Cc: | David Schwartz, [email protected]…, [email protected]… |
| Blocked By: | Blocking: |
Description
Testing type: Memory leaks
Short description: After refreshing the page several times the use of memory was increased and it was never free.
Steps to reproduce:
- Using Chrome, open the test_Slider page (/dijit/tests/form/test_Slider.html)
- Press F5 or refresh the page several times (i.e. 10)
Actual results: the use of memory was duplicated
Expected results: the memory should be free
Attachments (1)
Change History (5)
Changed 10 years ago by
| Attachment: | Slider_2_Chrome.jpg added |
|---|
comment:1 Changed 10 years ago by
| Cc: | [email protected]… removed |
|---|---|
| Component: | General → Dijit |
| Owner: | anonymous deleted |
| Summary: | When refreshing the test_Slider samples, the memory reserved is not released → Slider: memory leak on page refresh |
comment:2 Changed 10 years ago by
| Milestone: | tbd → 1.6 |
|---|---|
| Owner: | set to Douglas Hays |
comment:3 Changed 10 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
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).
comment:4 Changed 9 years ago by
| Component: | Dijit → Dijit - Form |
|---|
Note: See
TracTickets for help on using
tickets.
IBM #151591