Results 1 to 3 of 3

Thread: Huge memory leak

    Success! Looks like we've fixed this one. According to our records the fix was applied for DSGNR-996 in a recent build.
  1. #1
    Sencha Premium User lorezyra's Avatar
    Join Date
    Dec 2007
    Japan -- 千葉

    Exclamation Huge memory leak

    Designer version tested:
    • Designer 1.2.2.r48

    Operating System:
    • WinXP Pro

    • Ext JS 4.x
    • Ext JS 3.x

    • Designer does not release memory used by components when loading a new project. Designer continues to consume memory until it crashes. On WinXP, it will typically crash once memory usage exceeds 1GB RAM. Simply opening new projects without makes changes and without closing the XDS window will cause the application to become slow, unstable, and vulnerable to crashes.

    Test Case:


    Steps to reproduce the problem:
    • At the moment of initializing XDS, memory usage is about 60MB
    • Open a large(-ish) project - my 4.x project is over 640KB.
    • After opening my 640KB file, XDS memory usage is about 275MB.
    • Click preview (on any viewable class). XDS memory increases to 300MB.
    • Close preview and memory returns to about 275MB.
    • After previewing the same class a few times and closing the preview window each time, the memory usage increases about 10MB.
    • Open a new project (from File menu). This time I choose a small 65KB 4.x project.
    • Memory usage increases to 300MB. There is no apparent release of memory consumed by the previous project.
    • From File menu, Select open and reopen the same project (discard changes if needed). XDS memory usage increases again to 330MB.
    • From File menu, Select open recent and I selected the first opened large 4.x project (filesize= 640KB ). XDS memory usage balloons to 470MB!

    The result that was expected:
    • When opening a new project without closing Designer (aka XDS), all objects should be properly destroyed/deleted from memory.

    The result that occurs instead:
    • Memory isn't properly managed. XDS continues to consume memory until it finally crashes without saves and recourse.

    Screenshot(s) or Video:
    • none

    Debugging already done:
    • none

    Possible fix:
    • not provided
    Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection can never be obtained...

    When in doubt, check the d4mn source code!
    And here are my terms...

    1. I don't care if you use my source code. (Known as "Code.")
    2. I don't care if I get any monetary compensation.
    3. I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
    4. Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
    5. By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
    6. You are welcome to change and improve the Code to best meet your needs.
    7. I don't care if you use the Code in a commercial or open-source project.
    8. You are not required to contact me prior to using the Code.

    Simple. Enjoy.

  2. #2
    Sencha User aconran's Avatar
    Join Date
    Mar 2007


    Thanks for the report, we will look into this.
    Aaron Conran

  3. #3
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Olney, MD


    Wow nice report lorezyra

    awesome find!
    Phil Strong

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts