myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Bonicelli (JIRA)" <>
Subject [jira] Commented: (TRINIDAD-1030) IE7 memory leak
Date Wed, 02 Apr 2008 22:26:24 GMT


Davide Bonicelli commented on TRINIDAD-1030:

I set up a plain Trinidad page to run some tests and I've added a javascript function that
is invoked on "onunload".
The function sets to null all the global variables defined in Common1_0_X.js.

Running the page in sIEve without the script, shows how no memory is released when the page
is refreshed. When instead the script is added to the page, some of the memory is released.

This shows how Common1_0_X.js is leaking memory in IE.

The script probably breakes some Circular References and/or Closures.

You find the file with the script in the attachment files as "leak.jspx".

> IE7 memory leak
> ---------------
>                 Key: TRINIDAD-1030
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.5-core, 1.0.6-core, 1.0.7-core
>         Environment: IE7 running on Windows XP.
>            Reporter: Davide Bonicelli
>            Priority: Minor
> Pages generated with Trinidad can cause a memory leaks in IE7.
> This problem can be verified using sIEve to track the memory usage of IE while automatically
refreshing a page generated with Trinidad.
> The problem does not affect all the pages generated with Trinidad, thus it is probably
connected to some Trinidad tags.
> The bug can be reproduced running sIEve on the Trinidad Online Demo (
> It is possible to notice how pages like "index.jspx", "tree.jspx" and "outputText.jspx"
cause the memory leak.
> "componentDemos.jspx" is an example of page not causing memory leak.
> sIEve does not identify any memory leak in the affected pages, but the memory usage of
IE keeps increasing. The leakage could be then caused by what Microsoft describes as the "DOM
Insertion Order Leak Model" that is transparent to most leak-detection algorithms.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message