Wicket Throwing Out Of Memory Errors When AutomaticMultipleWindowSupport is set to true

2009-09-30 Thread Carlo Camerino
Hi,

I'm having problems . I think there is a bug in wicket in which the
memory usage zooms up exponentially when i copy and paste a url into a
new tab continuously.
This only happens when I explicity set automaticmultiplewindowsupport
to true. It seems to happen due to multiple page maps for the same
user.


For example I open in a browser

http://192.168.1.27:8010/loyalty/?wicket:interface=:1

I copy it to my clipboard, open a new tab, paste the url, open a new
tab, paste the url.
Tale note that the url changes in each tab...

Something like
http://192.168.1.27:8010/loyalty/?wicket:interface=:0-1
http://192.168.1.27:8010/loyalty/?wicket:interface=:1-1

I repeat this for a couple of times, and on the 9th or 10th iteration
the memory usage is way up afterwards I get an outofmemoryerror
already. (lack of heap space)
after checking the profiler, byte[] usage is way up. hundreds of
megabytes high.

I'm using wicket version 1.3.7

thanks
carlo

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket Throwing Out Of Memory Errors When AutomaticMultipleWindowSupport is set to true

2009-09-30 Thread Igor Vaynberg
try on 1.4.1 and see if you get the same result.

-igor

On Tue, Sep 29, 2009 at 11:16 PM, Carlo Camerino car...@sxchange.com.ph wrote:
 Hi,

 I'm having problems . I think there is a bug in wicket in which the
 memory usage zooms up exponentially when i copy and paste a url into a
 new tab continuously.
 This only happens when I explicity set automaticmultiplewindowsupport
 to true. It seems to happen due to multiple page maps for the same
 user.


 For example I open in a browser

 http://192.168.1.27:8010/loyalty/?wicket:interface=:1

 I copy it to my clipboard, open a new tab, paste the url, open a new
 tab, paste the url.
 Tale note that the url changes in each tab...

 Something like
 http://192.168.1.27:8010/loyalty/?wicket:interface=:0-1
 http://192.168.1.27:8010/loyalty/?wicket:interface=:1-1

 I repeat this for a couple of times, and on the 9th or 10th iteration
 the memory usage is way up afterwards I get an outofmemoryerror
 already. (lack of heap space)
 after checking the profiler, byte[] usage is way up. hundreds of
 megabytes high.

 I'm using wicket version 1.3.7

 thanks
 carlo

 -
 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