Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium Member
    Join Date
    Dec 2012
    Posts
    4
    Vote Rating
    1
    Richard.Spille is on a distinguished road

      1  

    Default Memory Leak on refresh ( IE9, HTML 5, ExtJS 3.4.0, ExtJS 4.1.1a Sandbox, No Iframe)

    Memory Leak on refresh ( IE9, HTML 5, ExtJS 3.4.0, ExtJS 4.1.1a Sandbox, No Iframe)


    REQUIRED INFORMATION

    Ext version tested:
    • ExtJS 4.1.1a Sandboxed with ExtJS 3.4.0
    Browser versions tested against:
    • IE9
    DOCTYPE tested against:
    • HTML 5
    Description:
    • Including ExtJS 4.x sandbox, ExtJS 3.4.0 base and ExtJS 3.4.0 all scripts in a blank HTML 5 document and refreshing page leaks ~20MB each refresh.
    Steps to reproduce the problem:
    • Page Refresh
    The result that was expected:
    • IE9 Memory Usage stays about the same after each refresh
    The result that occurs instead:
    • IE9 Memory Usage increases by ~20MB after each refresh
    Test Case:
    Code:
    <!DOCTYPE HTML>
    <html>
    <head>
        <script src="ext340-base-debug.js"></script>
        <script src="ext340-all-debug.js"></script>
        <script src="ext411-all-sandbox-debug.js"></script>    
    </head>
    <body>&nbsp;</body>
    </html>
    HELPFUL INFORMATION

    Debugging already done:
    • Remove the doctype - no leak
    • Remove ExtJS 4.x sandbox - no leak
    • Remove ExtJS 3.x base and all - no leak
    • Comment out fireDocReady in ExtJS 4.x sandbox - no leak
    Additional CSS used:
    • No CSS
    Operating System:
    • Windows 7

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    37,541
    Vote Rating
    872
    mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute mitchellsimoens has a reputation beyond repute

      0  

    Default


    Does this happen without sandbox?
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha Premium Member
    Join Date
    Dec 2012
    Posts
    4
    Vote Rating
    1
    Richard.Spille is on a distinguished road

      0  

    Default


    If you mean does it happen without the Ext4 sandbox script included, then no it does not leak.

    If you mean does it happen with Ext4 non-sandboxed included, then the answer is also no, it does not leak, however this is probably because of script errors triggered by running 3 & 4 together un-sandboxed.

  4. #4
    Ext JS Premium Member yuriy's Avatar
    Join Date
    Sep 2009
    Posts
    29
    Vote Rating
    0
    yuriy is on a distinguished road

      0  

    Lightbulb


    Hi, unfortunately I was also hit by this memory leak issue (and some other annoying things with sandbox).

    Richard did a very good job with tracking this down to "fireDocReady", so I just took it from there.
    Seems like the "MouseEnterLeave" test performed inside Ext.supports.init() call leaks in sandbox.

    I'll continue checking tomorrow, but so far it seems to be the reason.

    EDIT: I made a mistake with tests bisection (was too tired probably). It's not "MouseEnterLeave" as it turns out, but it's neightbour "GeoLocation", and specifically this beauty:
    typeof navigator.geolocation != 'undefined'
    Here's some read on this topic: https://github.com/Modernizr/Modernizr/issues/513
    Doing
    'geolocation' in navigator
    instead does not leak as it seems.

    PS: I only tested sandbox version, but seems this should leak in all cases - confirmed. I posted a separate bug report for this issue since it's not really sandbox related: http://www.sencha.com/forum/showthread.php?255148

Thread Participants: 2

Tags for this Thread