[
https://issues.apache.org/jira/browse/WICKET-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597050#action_12597050
]
Vincent MATHON commented on WICKET-1630:
----------------------------------------
Here are the relevant DOM nodes that are not released. As it is mostly heavy
resources (js files, css files) the leak cannot be neglected.
<SPAN class="yui-calcontainer single withtitle" id=i1Dp style="DISPLAY: none;
Z-INDEX: 99999; LEFT: 183px; POSITION: absolute; TOP: 144px"></SPAN>
<LINK id=yui__dyn_0
href="resources/org.apache.wicket.extensions.yui.YuiLib/calendar/assets/skins/sam/calendar.css"
type=text/css rel=stylesheet>
<SCRIPT id=yui__dyn_1
src="resources/org.apache.wicket.extensions.yui.YuiLib/yahoo-dom-event/yahoo-dom-event.js"
type=text/javascript ></SCRIPT>
<SCRIPT id=yui__dyn_2
src="resources/org.apache.wicket.extensions.yui.YuiLib/calendar/calendar-min.js"
type=text/javascript></SCRIPT>
<SCRIPT id=yui__dyn_3
src="resources/org.apache.wicket.extensions.yui.calendar.DatePicker/wicket-date.js"
type=text/javascript></SCRIPT>
<A class=calnavleft></A>
<A class=calnavright></A>
<IFRAME class=fixedsize style="FILTER: alpha(opacity=0); ZOOM: 1"
src="javascript:false;" ></IFRAME>
You can observe this leak easily by reloading the wicket Date example
(http://www.wicketstuff.org/wicket13/dates/) and looking at IE memory increase.
It is about 2 MO each time. I observe the leak only with IE 6, not with IE 7
or Firefox 2.x.
I didn't find a workaround yet.
Sincerly
Vincent MATHON
> memory leak with IE 6
> ---------------------
>
> Key: WICKET-1630
> URL: https://issues.apache.org/jira/browse/WICKET-1630
> Project: Wicket
> Issue Type: Bug
> Components: wicket-datetime
> Affects Versions: 1.3.3
> Environment: IE 6.0-2800-1106
> Reporter: Vincent MATHON
>
> I used Drip (http://www.outofhanwell.com/ieleak/index.php?title=Main_Page) to
> test the latest wicket date example (I suppose it is the 1.3.3 version) and
> I found several memory leaks with with IE 6. I reproduce the same behaviour
> with my own project using wicket-date-time 1.3.1.
> sincerly,
> Vincent MATHON
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
