Hybrid View

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha Premium Member
    Join Date
    Oct 2009
    Location
    Aylesbury, Bucks, UK
    Posts
    37
    Vote Rating
    5
    sytel is on a distinguished road

      0  

    Exclamation Possible memory leak with GridPanel and Store

    Possible memory leak with GridPanel and Store


    Ext version tested:
    • Ext 3.0.3
    • Ext 3.3.2
    • Ext 3.4.0
    Adapter used:
    • ext
    css used:
    • only default ext-all.css
    Browser versions tested against:
    • IE8
    • IE9
    • FF4.0.1
    • FF6.0.1
    • Chrome 10
    • Chrome 12
    Operating System:
    • Win 7 x64
    • WinXP Pro
    Description:
    • There is a definite memory increase when using GridPanel with a store. Every time the store is reloaded and grid is rendered, the browser consumes more memory and it does not seem to free it. Best example is IE, which can consume over 1GB and crash within 30 minutes using the attached code.
    Test Case:
    Working code is attached. Unzip it into ext/examples

    Steps to reproduce the problem:
    • Open Click on Autorefresh button
    • Observe memory consumption using e.g. sieve or Sysinternals Process Explorer
    The result that was expected:
    • Stable memory footprint
    The result that occurs instead:
    • Browser starts consuming memory until it crashes
    Debugging already done:
    • none
    Possible fix:
    • not provided
    Attached Files

  2. #2
    Sencha User
    Join Date
    Apr 2010
    Posts
    13
    Vote Rating
    0
    oniseijin is on a distinguished road

      0  

    Default Status?

    Status?


    I'm seeing this with EXT JS 4.0.7 as well.. basically calling store.load() refreshes the Grid, and the memory keeps being used (up to 1GB before the browser dies): IE + Firefox 5

  3. #3
    Sencha Premium Member
    Join Date
    Oct 2009
    Location
    Aylesbury, Bucks, UK
    Posts
    37
    Vote Rating
    5
    sytel is on a distinguished road

      0  

    Default


    Sencha Devs, have you gotten anywhere with this one? I suspect there may actually be two issues, one with record id's and another with reader. And yes, it's still present in Ext JS 4.x.

  4. #4
    Sencha User
    Join Date
    Apr 2010
    Posts
    13
    Vote Rating
    0
    oniseijin is on a distinguished road

      0  

    Default solution?

    solution?


    No replies yet, but I did find out that if I stopped doing the "load", the memory eventually did go down a bit. The bad news means that it might just be a standard javascript/browser/os interaction problem!

  5. #5

  6. #6
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    975
    Vote Rating
    110
    Daniil is a name known to all Daniil is a name known to all Daniil is a name known to all Daniil is a name known to all Daniil is a name known to all Daniil is a name known to all

      0  

    Default


    We are facing the same issue. It would be great to have any answer from ExtJS team.

  7. #7
    Sencha Premium Member
    Join Date
    Oct 2009
    Location
    Aylesbury, Bucks, UK
    Posts
    37
    Vote Rating
    5
    sytel is on a distinguished road

      0  

    Default


    Has anyone tried to apply suggestions from post #13?

  8. #8
    Sencha Premium Member Oliver Timm's Avatar
    Join Date
    Jan 2013
    Location
    Berlin
    Posts
    6
    Vote Rating
    2
    Oliver Timm is on a distinguished road

      0  

    Default


    The suggestions from post #13 arenĀ“t relevant for me because I have an xml store and all rows have an id. The problem of high increasing memory still exists.

  9. #9
    Sencha User
    Join Date
    Jan 2014
    Posts
    11
    Vote Rating
    0
    grdrew is on a distinguished road

      0  

    Default


    I have the same problem with a memory leak in a REST store in both v4 and v5.

    I create a v5 app using sencha cmd, added a REST store and a dynamic task in which I load/reload the store every 1 second, nothing else going on, just the load, but in less than a day both FF and chrome will crash because of the memory leak.

    It looked like a problem with the data.proxy.Rest reader, but it was to difficult to work out exactly what was leaking. In the end I decided to bypass the data.proxy.Rest reader and write my own simple XMLHttpRequest handler, manually loading the response into the store.

    This solved the leak in the store but now I have a chart linked to another store that is updating every 4 seconds and the chart seems to be leaking memory as well.

    Does everything in EXT leak? Any attempt at writing a serious SPA that's intended to run continually seems doomed to fail.

  10. #10
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,367
    Vote Rating
    136
    dongryphon is a splendid one to behold dongryphon is a splendid one to behold dongryphon is a splendid one to behold dongryphon is a splendid one to behold dongryphon is a splendid one to behold dongryphon is a splendid one to behold

      0  

    Default


    @grdrew -

    Can you post a fiddle (https://fiddle.sencha.com) for me to look at?
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"