[ http://issues.apache.org/jira/browse/FOR-591?page=all ]
David Crossley updated FOR-591:
-------------------------------
Summary: MaxMemory needs increasing for large document sets: Memory
Leak with XMLFileModule (was: MaxMemory needs increasing)
Description:
Since the docs restructuring for the 0.7 release it has become necessary to
increase the maxmemory to be able to build the Forrest site. We gained three
copies of the documents so suddenly have a large document set to trigger memory
leakage issues.
Possibly COCOON-1574 "Memory Leak with XMLFileModule".
Does someone have the tools to run some diagnostics?
(NB maxmemory has been increased in our site-author/forrest.properties, if we
resolve this issue it should be reduced again)
was:
Since the docs restructurng for the 0.7 release it has become necessary to
increase the maxmemory to be able to build the Forrest site.
Does this indicate a memory leak?
Does someone have the tools to run some diagnostics?
(NB maxmemory has been increased in forrest.properties, if we resolve this
issue it should be reduced again)
Changed the Issue Summary and Description.
> MaxMemory needs increasing for large document sets: Memory Leak with
> XMLFileModule
> ----------------------------------------------------------------------------------
>
> Key: FOR-591
> URL: http://issues.apache.org/jira/browse/FOR-591
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.7, 0.8-dev
> Reporter: Ross Gardler
> Priority: Blocker
> Fix For: 0.8-dev
>
> Since the docs restructuring for the 0.7 release it has become necessary to
> increase the maxmemory to be able to build the Forrest site. We gained three
> copies of the documents so suddenly have a large document set to trigger
> memory leakage issues.
> Possibly COCOON-1574 "Memory Leak with XMLFileModule".
> Does someone have the tools to run some diagnostics?
> (NB maxmemory has been increased in our site-author/forrest.properties, if we
> resolve this issue it should be reduced again)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
