On 6/7/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
The memory footprint is bothering me way more than the performance hit is tbh. I would be ok with keeping this if we clear it after rendering.
Another option might be to see if the stack trace could be compressed. I now keep the string representation of the filtered stack (not the complete stack trace). For instance, we could try to discover only filename + line number, or something similar. However, I think the number of components on your page is actually the biggest denominator here. Until we find a usecase for the creation of the stack elements at a later stage, I'm fine with killing the metadata for now. We have the ability for keeping it, so it is easily re-instated. Martijn -- Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.6 contains a very important fix. Download Wicket now! http://wicketframework.org
