[
https://issues.apache.org/jira/browse/TRINIDAD-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584883#action_12584883
]
Scott O'Bryan commented on TRINIDAD-1030:
-----------------------------------------
Davide,
Does this happen in FF? I know we've been very careful about closures in the
past and while I don't deny we have any, this test gives us no indication as to
where these closures might be. There may not even BE any closures as we don't
generally control when the browser garbage collects. It would be helpful to us
if you could:
1. Track down the closures and/or
2. Try to use a utility which forces garbage collection of the browsers rather
then relying on nulling things out. Explicitly nulling things out may be
triggering a gc in IE that would not happen otherwise.
Scott
> IE7 memory leak
> ---------------
>
> Key: TRINIDAD-1030
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1030
> 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
> Attachments: leak.jspx
>
>
> Pages generated with Trinidad can cause a memory leak 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
> (http://www.irian.at/trinidad-demo/faces/index.jspx).
> 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 the 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 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.
