[
https://issues.apache.org/jira/browse/WICKET-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604616#action_12604616
]
Niels Boeger commented on WICKET-1698:
--------------------------------------
Thanks for your fast response.
Concerning the AutoComplete example: I intended to refer to the
protected void onSubmit(AjaxRequestTarget target)
{
target.addComponent(label);
}
part of the very bottom of AutoCompletePage.java. Wickets JavaDoc talks about
updating instead of replacing for AjaxRequestTarget.onSubmit(), sorry if I was
misleading.
I added a screenshot from Drip showing the leaking elements of the AutoComplete
example app running in a local jetty. For that, I disabled Wicket AJAX
debugging by setting "getDebugSettings().setAjaxDebugModeEnabled(false);" in
the Ajax application (was true before). I double-checked that, and the Wicket
AJAX Debug link is not visible on the web page.
> IE7 memory leak when components are updated via AJAX
> ----------------------------------------------------
>
> Key: WICKET-1698
> URL: https://issues.apache.org/jira/browse/WICKET-1698
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.3, 1.4-M2
> Environment: WinXP SP3, IE7
> Reporter: Niels Boeger
> Assignee: Matej Knopp
>
> I noticed a large increase in IE7s memory consumption when a wicket component
> is updated via AJAX.
> In my case, I used wicket to update the markup of a html table. The table
> acts as datasource for a yui datatable. The markup update is triggered by a
> "wicketAjaxGet" request on the client, and Wicket updates the markup of the
> table.
> Drip (http://www.outofhanwell.com/ieleak/) shows that old markup is not
> garbage collected by IE7.
> YUI does not seem to be the culprit, the problem occured even when I removed
> all YUI code.
> Using Drip on the AutoComplete example
> (http://www.wicketstuff.org/wicket13/ajax/autocomplete) shows the same
> behavior.
> I tested this in my application with both Wicket 1.3.3 and Wicket 1.4-M2.
> FF2 (Mac OS X & WinXP), FF3RC2 (WinXP) and Safari 3.1 (Mac OS X) run fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
