Should be fixed in svn. Can you give it a try? -Matej
On Tue, Jul 21, 2009 at 8:58 AM, Tsutomu YANO <t_y...@me.com> wrote: > I created a JIRA: > > https://issues.apache.org/jira/browse/WICKET-2384 > > We finally found out the reason of this problem. This was a bug of Wicket > (on FeedbackPanel class). > I wrote a fixed code on the JIRA. > > I hope that the solution will be included in next release. This is big bug > for me. > > Thank you for your advice. > > --------------------- > Tsutomu YANO > t_y...@me.com > benbr...@mac.com > > > 09/07/20 (MON) 10：02AM、 "Jeremy Thomerson" <jer...@wickettraining.com> > said： > >I have not run your quickstart, but this sounds peculiar to me. > >Please create a JIRA (with the quickstart attached) and reply-all here > >with the issue URL. > > > >-- > >Jeremy Thomerson > >http://www.wickettraining.com > > > > > > > > > >On Sun, Jul 19, 2009 at 9:10 AM, Tsutomu Yano<t_y...@me.com> wrote: > >> Hi. > >> > >> When I uses component.info() method to display a message, my program > stopped by OutOfMemoryError or StackOverflowError. > >> I found the work around, but I could not found reason of this error. Can > anyone teach me the reason? > >> > >> > >> I create a sample application to show this problem. Open attached tar.gz > file(including a maven project) and run. > >> check 'submit continuously' checkbox and click 'register' button. > >> > >> The program will display current session size continuously. the size > will be increased, and finally program will be > >> stopped with OutOfMemoryError or StackOverflowError. > >> > >> > >> But if you changes only one line, this program will not be stopped. > >> > >> ---original code--- > >> private SubmitLink insertLink = new SubmitLink("insertLink") { > >> public void onSubmit() { > >> info("message"); > >> setResponsePage(new Test(testFormBean)); > >> Session session = Session.get(); > >> long size = session.getSizeInBytes(); > >> LOGGER.info("SESSION SIZE: {}", size); > >> } > >> }; > >> --------------------- > >> > >> ---changed---------- > >> private SubmitLink insertLink = new SubmitLink("insertLink") { > >> public void onSubmit() { > >> Session.get().info("message"); //CHANGED!!! > >> setResponsePage(new Test(testFormBean)); > >> Session session = Session.get(); > >> long size = session.getSizeInBytes(); > >> LOGGER.info("SESSION SIZE: {}", size); > >> } > >> }; > >> -------------------- > >> > >> > >> Component's 'info()' method will attache the component, to which > 'info()' method is called, as 'reporter' object of > >> FeedbackMessage object. It could become a reason of this problem. But > the FeedbackMessage will be destroyed when the message > >> will be displayed with FeedbackPanel. So I think, memory leak will never > occur. > >> > >> If I use 'Session.get().info()' method, instead of component.info(), > FeedbackMessage's 'reporter' object become null. > >> In this case, My sample program never stopped with OutOfMemoryError or > StackOverflowError. > >> > >> I could not find out the reason. Is this a bug of Wicket? or failure of > my program. > >> > >> > >> > >> > >> > >> --------------------------------------- > >> Tsutomu YANO > >> t_y...@me.com > >> > >> > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
