Changes between Version 1 and Version 2 of Ticket #7666, comment 1


Ignore:
Timestamp:
Sep 9, 2011, 3:56:55 AM (12 years ago)
Author:
peter.nystrom
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7666, comment 1

    v1 v2  
    1 After doing some tests, it seems that the memory leak started in jQuery UI 1.8.13. Could the fix for #7257 have anything to do with it? It was the only change to ui.core in this release, and is about caching attribute values instead of looking them up each time.
     1After doing some tests, it seems that the memory leak started in jQuery UI 1.8.13. By reverting the changes in #7256, the memory leak disappears. The tests were done with jQuery 1.6.2. Can someone verify?
    22
    33/Peter
    4 
    5 Replying to [ticket:7666 liminzhang]:
    6 > Hi there,
    7 >
    8 > I tested two blank pages on IE7
    9 >
    10 > The first page
    11 >
    12 > <head>
    13 >
    14 >     <script src="/jquery/1.6.2/jquery.min.js" type="text/javascript"></script> <script src="/jqueryui/1.8.16/jquery-ui.min.js" type="text/javascript"></script>
    15 >
    16 > </head> <body> </body>
    17 >
    18 > The second page
    19 >
    20 > <head>
    21 >
    22 >     <script src="/jquery/1.4.2/jquery.min.js" type="text/javascript"></script> <script src="/jqueryui/1.8.16/jquery-ui.min.js" type="text/javascript"></script>
    23 >
    24 > </head> <body> </body>
    25 >
    26 >     After each refreshing with F5, IExplore used 2 or 3 more megabytes memory with the first page. However it did not happen on the second page.
    27 >
    28 >     Does jQuery 1.6.2 bring memory leakage for jQuery UI library? It also happens on jQuery 1.5.1, 1.6.1.
    29 >
    30 >     Thanks
    31 >
    32 > Limin