[
https://issues.apache.org/jira/browse/TRINIDAD-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585132#action_12585132
]
Davide Bonicelli commented on TRINIDAD-1030:
--------------------------------------------
Scott,
when I say Common1_0_X.js leaks memory, I don't mean it has errors. In fact
FF doesn't present this problem.
Leaking is present only in IE thanks to the way Microsoft implemented it (two
garbage collectors that don't talk to each other).
What I'm trying to do is identify the circular references in the scripts or to
DOM objects to see if there's a way to break them. This kind of references are
absolutly correct from a programmer point of view, but IE doesn't know how to
handle them.
Even if we force IE to garbage collect I don't think it's going to make any
difference, because the IE gc is exactly what's "broken".
Please let me know if you have any idea or hint.
Bye
Davide
> 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.
