#493 closed defect (duplicate)
memory leak on firefox
| Reported by: | bill | Owned by: | anonymous |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | General | Version: | 0.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Every time test_Dialog.html is loaded, Firefox 1.5 leaks about 500K. Not sure if it's a dojo problem or firefox problem. IE seems to be OK. (Haven't tested Safari or Konqueror)
http://archive.dojotoolkit.org/nightly/tests/widget/test_Dialog.html
Change History (8)
comment:1 Changed 9 years ago by dylan
comment:2 Changed 9 years ago by alex
is it actually leaked? Or just allocated and then released when you navigate to a different page?
Leakage is when you keep refreshing the page and memory use *always* increases. You'll have to keep refreshing to find the right level-set to determine leakage. If one doesn't appear, you most likley have a real leak.
comment:3 Changed 9 years ago by bill
it's actually leaked.
When FF starts it's taking 27M. After loading test_Dialog.html is 29M. After refreshing multiple times it went to 35M. Returning to my non-dojo home page, memory usage remained at 35M.
comment:4 Changed 9 years ago by dylan
We should really use the memory leak tool, and test whether this is us or firefox. I know they have a bunch of memory leaks in bugzilla, and I don't think any of us have had time to look into those and know what the workarounds are.
comment:5 Changed 9 years ago by dmachi
- Milestone changed from 0.3release to 0.4
comment:6 Changed 9 years ago by tonyissakov@…
See ticket #1041.
comment:7 Changed 9 years ago by bill
- Resolution set to duplicate
- Status changed from new to closed
Dup of #1041
have you tried testing with the memory leak tool, http://dbaron.org/log/2006-01#e20060114a