Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: [4.2.1 GA] Memory leaks with iframes

    Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    1,018

    Default [4.2.1 GA] Memory leaks with iframes

    REQUIRED INFORMATION

    Ext version tested:

    • Ext 4.2.1 GA

    Browser versions tested against:
    • Chrome 27.0.1453.94 m
    • FireFox 21.0
    • IE9 9.0.8112.16421 (update 9.0.15 (KB2817183))

    DOCTYPE tested against:
    • <!DOCTYPE html>

    Description:
    • Memory leaks if load an iframe into a Window. The results of the below test case:

    IE9 30 MB => 58 MB
    FireFox 102 MB => 118 MB (wait a bit, FireFox slowly releases the memory)
    Chrome 69 MB => 135 MB

    • The related threads:

    Steps to reproduce the problem:
    • Open the test case in some browser and notice the consumed memory in the Task Manager
    • Click the Button 10 times
    • Close all the Windows
    • Notice the consumed memory in the Task Manager

    The result that was expected:
    • The consumed memory goes back (at least, near) to the initial state

    The result that occurs instead:
    • The consumed memory increased and doesn't get released.

    Test Case:

    outer.html
    Code:
    <!DOCTYPE html>
    <html>
    <head>
        <title>Memory leask with iframes</title>
    
        <link rel="stylesheet" href="../resources/css/ext-all.css" />
        
        <script src="../ext-all-debug.js"></script>
    
        <script>
            var counter = 0;
    
            var open = function (index) {
                var url = 'inner.html?idx=' + index,
                    win = new Ext.Window({
                        id: "Window" + index,
                        closeAction: 'destroy',
                        layout: "fit"
                    }),
                    iframeObj = {
                        tag: "iframe",
                        id: win.id + "_IFrame",
                        name: win.id + "_IFrame",
                        src: url,
                        frameborder: 0
                    },
                    iframeCt = {
                        xtype : "component",
                        autoEl: iframeObj
                    };
    
                win.add(iframeCt);
                win.show();
            };
    
            Ext.onReady(function () {
                Ext.create("Ext.button.Button", {
                    renderTo: Ext.getBody(),
                    text: "Open",
                    handler: function () {
                        open(window.counter++);
                    }
                });
            });
        </script>
    </head>
    <body>
    
    </body>
    </html>
    inner.html
    Code:
    <!DOCTYPE html>
    <html>
    <head>
        <title>Inner</title>
    
        <link rel="stylesheet" href="../resources/css/ext-all.css" />
        
        <script src="../ext-all-debug.js"></script>
    </head>
    <body>
        Hello from iframe!
    </body>
    </html>


    HELPFUL INFORMATION


    Operating System:

    • Windows 7 SP1 64bit
    Last edited by Daniil; 31 Jul 2013 at 10:50 PM. Reason: Spelling
    Object.NET
    Frameworks and Tools for .NET Developers
    --------------------------------------------------
    Ext.NET - Ext JS for ASP.NET - Examples | Twitter
    Bridge.NET - Write C#. Run JavaScript! - Live | Twitter
    --------------------------------------------------

  2. #2
    Sencha User slemmon's Avatar
    Join Date
    Mar 2009
    Location
    Boise, ID
    Posts
    6,165

    Default

    Thanks for the report! I have opened a bug in our bug tracker.

  3. #3
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    1,018

    Default

    Hi @slemmon,

    Could you shed some light on the status of the issue? Is it being considered as a severe one? It looks a 100% showstopper for applications where ExtJS is used in iframes. Is there any time frame? Any findings?
    Object.NET
    Frameworks and Tools for .NET Developers
    --------------------------------------------------
    Ext.NET - Ext JS for ASP.NET - Examples | Twitter
    Bridge.NET - Write C#. Run JavaScript! - Live | Twitter
    --------------------------------------------------

  4. #4
    Sencha User
    Join Date
    Jul 2013
    Posts
    1

    Default Memory leak problem

    Hi @slemmon


    As Coretech team, we are licenced customer and faced the same problem. Ext.net refers you as a solution address.
    We recently improved the pages from Ext.Net 1.2 to 2.2 by spending so much effort. Our customers are giving us negative feedback these days due to memory leak bug
    after this improvement. We are in quite hard situation.


    As a team, we will decide to get the old version by spending the same effort or will wait for your response in patience.
    Is there any development about the issue? and could you give me a date for solution?


    We're looking forward to hearing from you.


    Best Regards.

  5. #5
    Sencha Premium Member
    Join Date
    Nov 2011
    Posts
    72

    Default

    Iframe issues are hard to fix, since there could be several causes spread over the entire framework. I wouldn't expect an official response on this right away.

    As far as testing goes, you might want to use Ext.ux.Iframe instead of using autoEl, although I'm fairly certain the issue will still exist.

  6. #6
    Sencha User Daniil's Avatar
    Join Date
    Jun 2010
    Location
    Saint-Petersburg, Russia
    Posts
    1,018

    Default

    Hi @eric.cook,

    Thank you for the input.

    Yes, you are right, the results with Ext.ux.IFrame (which, by the way, uses renderTpl instead of autoEl to render an iframe) are not better. They even look much worse in IE. Though it might be caused by recent Windows update

    IE9 37 MB => 157 MB
    Chrome 74 MB => 132 MB

    Here is a test case. The inner.html stays without changes.

    outer with Ext.ux.IFrame.html
    Code:
    <!DOCTYPE html>
    <html>
    <head>
        <title>Memory leask with iframes</title>
    
        <link rel="stylesheet" href="../resources/css/ext-all.css" />
        
        <script src="../ext-all-debug.js"></script>
    
        <script>
            var counter = 0;
    
            Ext.Loader.setPath('Ext.ux', '../examples/ux');
            Ext.require('Ext.ux.IFrame');
    
            var open = function (index) {
                var url = 'inner.html?idx=' + index,
                    win = new Ext.Window({
                        id: "Window" + index,
                        closeAction: 'destroy',
                        layout: "fit",
                        items: [{
                            xtype: "uxiframe",
                            src: url
                        }]
                    });
    
                win.show();
            };
    
            Ext.onReady(function () {
                Ext.create("Ext.button.Button", {
                    renderTo: Ext.getBody(),
                    text: "Open",
                    handler: function () {
                        open(window.counter++);
                    }
                });
            });
        </script>
    </head>
    <body>
    
    </body>
    </html>
    Object.NET
    Frameworks and Tools for .NET Developers
    --------------------------------------------------
    Ext.NET - Ext JS for ASP.NET - Examples | Twitter
    Bridge.NET - Write C#. Run JavaScript! - Live | Twitter
    --------------------------------------------------

  7. #7
    Sencha User
    Join Date
    Jul 2013
    Posts
    1

    Default Any progress or time frames

    Dear Senscha Support,

    This issue has very severe consequences on our side, considering that our products are SaaS. In practice we are unable to use recent versions of your library or any library tied to these. It would be extremely helpful if we can get a time frame for the solution of these iframe related bugs, because right now all cross browser migration coding has stopped and we are under enormous pressure from our management and customers.

    Best Regards,
    Arslan Arslan
    Logo Business Solutions

  8. #8

    Default Timescales

    We are currently being hit hard with this memory leak issue to the point where it is now costing our company money and clients as a result. Not to mention the man hours spent trying to implement work-arounds.

    Please can an update be posted on this issue as it has been in existence for some time with no update.

    I would appreciate some sort of response to this post, even if it is to say that no-one is looking at it. We can then look at moving away from the EXT JS stack due to lack of confidence in the technology.

    Thanks
    Chris.

    Software Manager
    Dezrez

  9. #9
    Sencha User
    Join Date
    Mar 2010
    Posts
    3

    Default

    Dear Sencha Team,

    We were moving our MVC applitacion, in a very long and hard work, from ExtJS 3.X framework to the new ExtJS 4.X version.

    We spent a lot of money, time and resources in this migration process, and also implementing new complex functionalities. Now, we are ready to launch our application to market but we can't go ahead with this huge problem. That's completely unusable for any of our clients.

    This is a critical and urgent issue for us, as this makes us impossible to release our new product version.

    So, in order to determine our corporate strategy, we would like to know if you have any information about what is the current status of this bug or if you have any roadmap or estimated date to get it solved.

    Thanks.
    Last edited by jareyes; 26 Aug 2013 at 1:43 AM. Reason: Syntax

  10. #10
    Sencha User
    Join Date
    Mar 2010
    Posts
    3

    Default

    Hi again,

    I think many users would appreciate any kind of response from Sencha Team regarding this issue, even to say that this bug will never be solved, so in this way everyone could take his own decision. That's better than keep in silence.

    Thanks.

Page 1 of 2 12 LastLast

Posting Permissions

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