Bug Tracker

Changes between Version 1 and Version 2 of Ticket #8171, comment 6


Ignore:
Timestamp:
Feb 3, 2011, 7:04:42 PM (11 years ago)
Author:
smudgeface
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8171, comment 6

    v1 v2  
    11Sorry, I should know better than to file partial bug reports.
    22
    3 Methodology:
    4 -load up [http://jsfiddle.net/rJ8x5/8/]
    5 
    6 -watch memory usage using Sysinternals Process Explorer or Windows Task Manager
    7 
     3'''Methodology:'''[[BR]]
     4-load up [http://jsfiddle.net/rJ8x5/8/][[BR]]
     5-watch memory usage using Sysinternals Process Explorer or Windows Task Manager[[BR]]
    86-refresh the page
    97
    10 Expected Outcome:
     8'''Expected Outcome:'''[[BR]]
    119-Stable memory usage
    1210
    13 Visible Outcome:
    14 
    15 -Memory continues to increase as long as page is open
    16 
    17 -Refreshing the page '''does not''' free up all consumed memory
    18 
     11'''Visible Outcome:'''[[BR]]
     12-Memory continues to increase as long as page is open[[BR]]
     13-Refreshing the page '''does not''' free up all consumed memory[[BR]]
    1914-this indicates both a pseudo-leak as well as an IE cross-page leak
    2015
    21 Reproducibility:
    22 -This is highly reproducible in IE8 as well as IE8 (compat) and IE7
    23 -I am unable to test in IE6
     16'''Reproducibility''':[[BR]]
     17-This is highly reproducible in IE8 as well as IE8 (compat) and IE7[[BR]]
     18-I am unable to test in IE6[[BR]]
    2419-Not reproducible in Webkit/Mozilla
    2520
    26 jQuery History:
    27 
    28 -Using jsfiddle I was able to confirm that the leak exists on all major releases of jQuery, back to 1.3.2 (see note)
    29 
     21'''jQuery History:'''[[BR]]
     22-Using jsfiddle I was able to confirm that the leak exists on all major releases of jQuery, back to 1.3.2 (see note)[[BR]]
    3023-I updated my original link to include actual DOM insertion [http://jsfiddle.net/rJ8x5/8/]
    3124
    3225
    33 note: The fact that this issue exists using old versions of jQuery is alarming to me. Either there is a fundamental problem with the way I am creating the inner closure, or there is a fundamental problem with jQuery. I am unable to see anything wrong with my code, however...
     26''note: The fact that this issue exists using old versions of jQuery is alarming to me. Either there is a fundamental problem with the way I am creating the inner closure, or there is a fundamental problem with jQuery. I am unable to see anything wrong with my code, however...''