[ http://issues.apache.org/jira/browse/MYFACES-309?page=comments#action_12317491 ]
Bruno Aranda commented on MYFACES-309: -------------------------------------- I think we should contact the jscookmenu javascript author, Heng Yuan (http://www.cs.ucla.edu/~heng/JSCookMenu/), with this issue (Werner, could you do that?). Once he fixes this issue we could include the new javascript to the myfaces codebase. > JSCookmenu browser leak > ----------------------- > > Key: MYFACES-309 > URL: http://issues.apache.org/jira/browse/MYFACES-309 > Project: MyFaces > Type: Bug > Environment: myfaces 1.0.9 > Reporter: Werner Punz > > Hi I know I am picky.... > But has anyone checked the more dynamic components for mem leaks. > After having spent several hours yesterday to remove some of those dreaded > leaks in my ajax component on sourceforge. > I ran the test against the jscookmenu today and got the painful result of > several component leaks. > The problem in those cases is not how that the javascripts are incorrect but > that the browsers basically cause so called component leaks once you have a > cyclic reference between a global javascript object and one from the dom tree. > (at least the IE does dunno about the Moz) > The problem unfortunately is well known and called mem leak bug and since a > few days there is a good tool at least on windows to detect them, which is > called drip . > http://jgwebber.blogspot.com/2005/05/drip-ie-leak-detector.html > Given my experiences from yesterday, debugging my own stuff, I can say, that > I trust the results from drip regarding leaked components, they resemble my > experiences and errors I did myself. > It is not a big bug, but given that some webapps probably use the jscookmenu > for hours, it is nasty enough, to be fixed in the long run. > The problem with the mem leak bug is, that a page change does not recycle the > leaked objects only a closing of the browser does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
