Hopefully I can recreate in a quickstart. The pages in our app are
dynamically created. If this leak is somehow related to how the layout
engine works it might be difficult. I'll see what I can do.
-----Original Message-----
From: Jeremy Thomerson
Sent: Wednesday, November 10, 2010 5:23 PM
To: users@wicket.apache.org
Subject: Re: Memory Leak in 1.4.13?
On Wed, Nov 10, 2010 at 5:57 PM, Brad Grier
<brad.gr...@salusnovus.com>wrote:
I recently upgraded our app from 1.4.12 to 1.4.13. Our app has an admin
screen that shows the current session size using Session’s getSizeInBytes
method. This screen is just a panel that gets replaced/refreshed via Ajax
when a link is clicked. Today I noticed that every time I clicked the link
to reload the panel the session size grows by around 3000 KB and never
does
a gc. If I roll back to 1.4.12 and the problem goes away.
In the Netbeans profiler, the only thing I see spiraling out of control
are
byte[] objects (serialized objects?). Nothing unusual appears with the
size
or number of my application specific objects. For now I’m rolling back to
1.4.12 as I’m not sure how this is affecting things outside this specific
screen.
Thanks.
Please create a quickstart and see if you can reproduce this. If you can,
attach it to a JIRA. We'll fix it.
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
