[
https://issues.apache.org/jira/browse/WICKET-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400463#comment-13400463
]
Fyodor Kupolov commented on WICKET-1186:
----------------------------------------
Hi guys,
FYI, the change in
#[5987919|http://svn.apache.org/viewvc/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js/?rev=598791&view=diff&r1=598791&r2=598790&p1=/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js&p2=/wicket/trunk/jdk-1.4/wicket/src/main/java/org/apache/wicket/ajax/wicket-ajax.js]
sometimes leads to NoModificationAllowedError on IE10 release preview:
{code}
+ element.outerHTML = "";
+ element = "";
{code}
I believe, for this case it's safer to wrap this statement with try/catch and
ignore the error.
> Ajax Memory Leak in IE
> ----------------------
>
> Key: WICKET-1186
> URL: https://issues.apache.org/jira/browse/WICKET-1186
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-rc1
> Environment: Win XP
> IE 6
> Reporter: Nick Wiedenbrueck
> Assignee: Matej Knopp
> Fix For: 1.3.0-rc2
>
> Attachments: WicketIEMemLeak.zip
>
>
> Memory Leak in IE6 (IE7?) when using a DataView with AjaxPagingNavigator and
> each entry of the DataView table contains an AjaxLink. Memory increases by
> more than 500KB when displaying 100 items per page. AjaxDebugMode is
> disabled. Configuration is set to deployment. Version 1.2.6 is working fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
