Yeah, i think this is worth filing a bug report. It's great that things work correctly with caching on, but it still sounds like something is funky there.
On Wed, May 16, 2012 at 2:03 AM, Marnix Bindels <[email protected]> wrote: > Hi all, > > I was testing a template collection that uses #parse inside some #foreach, > which worked all fine inside eclipse but crashed when used in the stand-alone > application running with a low heap setting with an OutOfMemoryError: Java > heap space. I was able overcome this by setting the > <loader>.resource.loader.cache to "true". > > Still I wanted to let you know about this as it may be an indicator of a > resource management issue of sorts anyway. The parsed resource is constant, > with caching off it gets reported as found and loaded by the ResourceManager > for each iteration (some 6000 times in the example). I understand that > without caching it gets loaded every time, but why do the previously loaded > instances keep occupying memory? Perhaps by design: with proper caching in > place, this is not an issue. If not and you're interested: let me know > whether I should file a bug report/send in the examples. > > Thanks, > Marnix --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
