Uwe Schäfer wrote: > > Hi Artur, > > I suppose it isn´t the AppendingStringBuffer that is causing your problem. > Did you attach a profiler? http://YourKit.com is just one example of a > good, easy to setup&run profiler. > > I did like you said. I turns out that my refreshView consume so much memory but it still don't know if it is correct for the wicket app or not?
Ok, so I have a RefreshingView. This repeater contains about 300 rows. Every row contains about 20 ajax components (AjaxLinks, AjaxButtons, AjaxEditableLabels, ModalsWindows). Components have references to each other because clicking on one can change state of another (using AjaxRequestTarget). With every change, especially when opening ModalWindow, free memory drops approx. 20MB. (org.apache.wicket.protocol.http.pagestore.DiskPageStore retained size is about 27MB just after few clicks). When I force gc used memory drops to 50MB which is the same value as the application starts. So I think this is a prove that I don't hold references to unused objects :) So my question is. Am i doing something wrong or it is normal for wicket to consume so much memory when using so many ajax components on one page? Thanks in advance Artur -- View this message in context: http://www.nabble.com/OutOfMemoryError%3A-Java-heap-space---AppendingStringBuffer-tp14525029p14548202.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
