. 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
On Wed, Nov 10, 2010 at 5:57 PM, Brad Grier brad.gr...@salusnovus.comwrote:
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
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.comwrote:
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
