Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#20 OutOfMemoryError needs context or memory leak?

closed
None
3
2003-11-04
2003-11-03
Ralf Hauser
No

all of a sudden, I get this error (depending on whether
I add other tasks, it already dies after 177 files...).

I am not so sure that really have a self-calling macro
or whether there is a memory leak somewhere.

Therefore, please provide some context in which user
macro it fails!

at least when I change my ant start script with -Xmx256m
it no longer fails... ?

===============================================================================
END OF PROCESSING SESSION

Summary:
183 executed + 0 copied = 183 total
1 error(s), 2 warning(s)
Time elapsed: 30.5 seconds

WARNING! Processing session was interrupted:

> Source file:
n_listall_de.jsf
> Exception:
fmpp.ProcessingException: java.lang.OutOfMemoryError
Caused by: java.lang.OutOfMemoryError
> Java stack trace:
fmpp.ProcessingException: java.lang.OutOfMemoryError
at fmpp.Engine.processFile(Engine.java:536)
at fmpp.Engine.process(Engine.java:237)
at fmpp.tools.AntTask.execute(AntTask.java:547)
at org.apache.tools.ant.Task.perform(Task.java:341)

Discussion

  • Logged In: YES
    user_id=546667

    Ugh... it's again that if FreeMarker doesn't give me info about
    this, then I can't solve it on the FMPP side. But... did you snip
    the end of the log file, or there was really no more stack
    trace? It can be helful to see the stack trace of the
    OutOfMemoryError.

     
    • priority: 5 --> 3
    • assigned_to: nobody --> ddekany
     
  • Ralf Hauser
    Ralf Hauser
    2003-11-03

    Logged In: YES
    user_id=266141

    no, this was not the end of the stacktrace, but since it was
    neither freemarker, nor fmpp files, I thought not to need to
    cite them. Can't get it with 0.9.0 (since expert="no")
    doesn't work, but also, I cannot reproduce it since I since
    probably have changed my macro structure not knowingly such
    that it doesn't occur anymore... :(

    Sorry!

     
    • status: open --> closed
     
  • Logged In: YES
    user_id=546667

    Well, the stack trace has probably contained a "Caused by"
    listing that would show where the OutOfMemory itself has
    happened... eh... too late. Anyway, I hope the "expert" issue
    has been solved since then.