#11595 closed defect (invalid)
FilteringSelect: 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, tmayeur@…, hwcdl@… |
| Blocked By: | Blocking: |
Description
Testing type: Memory leaks
Widget: Filtering Select
After refreshing the page several times the use of memory increases and it was never free.
Steps to reproduce:
- Using Chrome, open the Filtering Select page
- Press F5 or refresh the page several times (i.e. 10)
Actual results: the use of memory increases and it was not free
Expected results: the memory should be free every time that the page is refreshed
Attachments (1)
Change History (5)
Changed 9 years ago by
| Attachment: | Filtering_2_Chrome.GIF added |
|---|
comment:1 Changed 9 years ago by
| Cc: | bkeese@… removed |
|---|---|
| Summary: | Memory used is increased every time that the page using filtering select widget is refreshed → FilteringSelect: memory leak on page refresh |
comment:2 Changed 9 years ago by
| Milestone: | tbd → 1.6 |
|---|---|
| Owner: | set to Douglas Hays |
comment:3 Changed 9 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This is a invalid test. See #11599.
comment:4 Changed 8 years ago by
| Component: | Dijit → Dijit - Form |
|---|
Note: See
TracTickets for help on using
tickets.
IBM #151573