Velocity
  1. Velocity
  2. VELOCITY-826

OutOfMemoryError using #parse and resource.loader.cache off

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.7
    • Fix Version/s: None
    • Component/s: Engine
    • Labels:
      None
    • Environment:
      Windows, Java 1.6, low heap (-Xmx10m)

      Description

      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?

      When published on teh dev mailing list, it was suggested to file this bug report.

      1. VelocityOutOfMemoryTest.java
        1 kB
        Marnix Bindels
      2. script_3.vm
        0.0 kB
        Marnix Bindels
      3. script_2.vm
        0.0 kB
        Marnix Bindels
      4. script_1.vm
        0.1 kB
        Marnix Bindels

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Marnix Bindels
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development