Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    IE + iFrame - Possible memory leak



    SmartClient version: SmartClient_v91p_2016-01-21_LGPL
    OS: Windows 7
    Browser: MSIE 11

    In our tests, we set up a clean VM as follow:
    Pagination: off
    RAM memory: 2048MB
    Windows: 7
    Core: 2
    VM provided by Microsoft at: https://dev.windows.com/en-us/microsoft-edge/tools/vms/

    Previous post:

    This is a post close to other one that addressed part of our leak:

    http://forums.smartclient.com/forum/...le-memory-leak

    On this previous post we solve an issue only on listgrid, now the issue is on iFrames and of course IE.

    Details:

    Our application needs to stay open for at least 8h without the need to close and open the browser again.

    Currently, we need to close and re-open the browser every 3h or less.

    We load the code in the browser as a usual user (without any developer tool). And leave the VM open. After some time, the OS will ask to close MSIE due to low memory. If we keep with the test running the OS logs

    We did several rounds and at the average with this code we faced a leak around 1.8 MB per minute

    The code below is a code similar to what we have and is the one used in our tests:
    http://pastebin.com/1XkprKSQ

    Can you guys please check for any memory leak in this scenario?
    Last edited by ueng; 26 Jan 2016, 17:12.

    #2
    This test repeatedly creates iframes and destroys them, and doing this is known to leak memory in IE, with no known solution (regardless of the framework used).

    There is a known technique that may reduce the amount of memory leaked per iframe, depending on the content of the iframe. However, as you'll note in the comments, whether it has any effect is based on what's in the iframe, and the technique is known to fail completely for many common types of content.

    You're welcome to try out the technique to see if it helps with the content you're loading (which we don't have), but we can't accept this as a bug, as it's obviously intractable.

    What we'd recommend is to switch to some other way of loading the HTML content if possible.



    Comment

    Working...
    X