Re: Ajax Memory Leak in IE
Matej, could the below exception also be caused by regression? This is the stack trace: 03ms server time taken for request app/?wicket:interface=:0:body:panel:leftToSellTab:panel:inventoryButtons:mainForm::IFormSubmitListener:: response size: 155862 [16:34:31.408] ERROR [http-8080-Processor6] RequestCycle - component body:panel:leftToSellTab:panel:inventoryList:inventoryLinesDynamic:38:villaTypes:2 not found on page ro.isdc.centerparcs.dpa.ui.page.DPADashboardPage[id = 0], listener interface = [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] org.apache.wicket.WicketRuntimeException: component body:panel:leftToSellTab:panel:inventoryList:inventoryLinesDynamic:38:villaTypes:2 not found on page ro.isdc.centerparcs.dpa.ui.page.DPADashboardPage[id = 0], listener interface = [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:411) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:456) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1152) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1248) at org.apache.wicket.RequestCycle.request(RequestCycle.java:489) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:343) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:193) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:217) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:106) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:229) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148) at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Thank you! Regards, Alex. Matej Knopp-2 wrote: Hi, sorry, it was a regression. Should be fixed in current trunk. -Matej -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14151752 Sent from
Re: Ajax Memory Leak in IE
Matej, could the below exception also be caused by regression? This is the stack trace: 03ms server time taken for request app/?wicket:interface=:0:body:panel:leftToSellTab:panel:inventoryButtons:mainForm::IFormSubmitListener:: response size: 155862 [16:34:31.408] ERROR [http-8080-Processor6] RequestCycle - component body:panel:leftToSellTab:panel:inventoryList:inventoryLinesDynamic:38:villaTypes:2 not found on page ro.isdc.centerparcs.dpa.ui.page.DPADashboardPage[id = 0], listener interface = [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] org.apache.wicket.WicketRuntimeException: component body:panel:leftToSellTab:panel:inventoryList:inventoryLinesDynamic:38:villaTypes:2 not found on page ro.isdc.centerparcs.dpa.ui.page.DPADashboardPage[id = 0], listener interface = [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:411) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:456) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1152) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1248) at org.apache.wicket.RequestCycle.request(RequestCycle.java:489) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:343) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:193) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:264) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:217) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:106) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:229) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148) at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Thank you! Regards, Alex. Matej Knopp-2 wrote: Hi, sorry, it was a regression. Should be fixed in current trunk. -Matej -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14151753 Sent from
Re: Ajax Memory Leak in IE
. Matej Knopp-2 wrote: Hi, sorry, it was a regression. Should be fixed in current trunk. -Matej -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14151753 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Thank you! Regards, Alex. Matej Knopp-2 wrote: Hi, sorry, it was a regression. Should be fixed in current trunk. -Matej -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14151753 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14155133 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Thank you! Regards, Alex. Matej Knopp-2 wrote: Hi, sorry, it was a regression. Should be fixed in current trunk. -Matej -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14151753 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14155133 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a14156069 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
/span/a /span /tdtd span29/09/2007/span /tdtd span07/04/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:9:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=odd td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRM67/span /span/a /span /tdtd span26/09/2007/span /tdtd span01/04/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=even td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRB27/span /span/a /span /tdtd span21/09/2007/span /tdtd span25/03/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /tr /tbody tfoot /tfoot /table]]/component/ajax-response INFO: Response parsed. Now invoking steps... ERROR: Error while parsing response: Erreur d'exécution inconnue INFO: Invoking post-call handler(s)... INFO: Invoking failure handler(s)... Antoine Angénieux a écrit : Just updated and rebuilt from the trunk, and now Ajax the pager component in AjaxFallbackDefaultDataTable do not work any more... (IE6 and IE7) Cheers, Antoine. picknick a écrit : Wow, you're quick. Thanks. Matej Knopp-2 wrote: Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
::ILinkListener::span img src=img/patients/crf.gif border=0/spanBMA97/span /span/a /span /tdtd span29/09/2007/span /tdtd span07/04/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:9:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=odd td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRM67/span /span/a /span /tdtd span26/09/2007/span /tdtd span01/04/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=even td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRB27/span /span/a /span /tdtd span21/09/2007/span /tdtd span25/03/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /tr /tbody tfoot /tfoot /table]]/component/ajax-response INFO: Response parsed. Now invoking steps... ERROR: Error while parsing response: Erreur d'exécution inconnue INFO: Invoking post-call handler(s)... INFO: Invoking failure handler(s)... Antoine Angénieux a écrit : Just updated and rebuilt from the trunk, and now Ajax the pager component in AjaxFallbackDefaultDataTable do not work any more... (IE6 and IE7) Cheers, Antoine. picknick a écrit : Wow, you're quick. Thanks. Matej Knopp-2 wrote: Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
Just updated and rebuilt from the trunk, and now Ajax the pager component in AjaxFallbackDefaultDataTable do not work any more... (IE6 and IE7) Cheers, Antoine. picknick a écrit : Wow, you're quick. Thanks. Matej Knopp-2 wrote: Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=odd td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRM67/span /span/a /span /tdtd span26/09/2007/span /tdtd span01/04/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:10:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /trtr class=even td span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:1:cell:link::ILinkListener::span img src=img/patients/crf.gif border=0/spanRB27/span /span/a /span /tdtd span21/09/2007/span /tdtd span25/03/2008/span /tdtd span a href=?wicket:interface=:1:portletFu1:fu1:table:rows:11:cells:4:cell:link::ILinkListener::span img src=img/patients/newevent.gif border=0/ /span/a /span /td /tr /tbody tfoot /tfoot /table]]/component/ajax-response INFO: Response parsed. Now invoking steps... ERROR: Error while parsing response: Erreur d'exécution inconnue INFO: Invoking post-call handler(s)... INFO: Invoking failure handler(s)... Antoine Angénieux a écrit : Just updated and rebuilt from the trunk, and now Ajax the pager component in AjaxFallbackDefaultDataTable do not work any more... (IE6 and IE7) Cheers, Antoine. picknick a écrit : Wow, you're quick. Thanks. Matej Knopp-2 wrote: Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
Wow, you're quick. Thanks. Matej Knopp-2 wrote: Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13990649 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
Hi, should be fixed in latest trunk. -Matej On Nov 26, 2007 5:24 PM, picknick [EMAIL PROTECTED] wrote: Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ajax Memory Leak in IE
I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ajax Memory Leak in IE
Here's the jira issue. Currently i can't say anything about IE7. https://issues.apache.org/jira/browse/WICKET-1186 https://issues.apache.org/jira/browse/WICKET-1186 Matej Knopp-2 wrote: Does it happen for IE6 only or also for IE7? Can you create a jira issue and attach a quickstart? -Matej On Nov 26, 2007 12:19 PM, picknick [EMAIL PROTECTED] wrote: I'm using a DataView-Table with an AjaxPagingNavigator listing 100 items per page. Each item has an AjaxLink to a detail view. When paging through the list the memory usage of the IE is increased by about 500 KB per page. Without the ajax link it's doing well. AjaxDebugMode is disabled. Configuration is set to deployment. Currently I'm using Wicket 1.3.0-rc1. I tried Wicket 1.2.6, which is working fine. Any ideas? Nick -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13947927 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Ajax-Memory-Leak-in-IE-tf4874611.html#a13953000 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
