[ http://jira.magnolia.info/browse/MAGNOLIA-1580?page=all ]
Philipp Bracher updated MAGNOLIA-1580:
--------------------------------------
Summary: memory: potential memory leak when deleting node (was: Memory
leak)
I think this is because derby/jackrabbit caches objects for reusing them, but
profiling could be a good idea.
could be a typo: use JAVA_OPTS instead of JAVA_OPS
> memory: potential memory leak when deleting node
> ------------------------------------------------
>
> Key: MAGNOLIA-1580
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1580
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.0.2
> Environment: windows XP, 2003
> Reporter: Marcin Oscieck
> Assigned To: Boris Kraft
> Attachments: tomcat.log
>
>
> When removing nodes from the repository memory footprint grows to 200Mb.
> Once tomcat is restarted footprint goes up to 117Mb.
> Replicable
> 1. Download 3.0.2 bundle
> 2. Extract it
> 3. Changed catalina.bat by adding (right below top header)
> JAVA_OPS=-Xmx512m
> 4. Go to: http://localhost:8080/magnoliaAuthor
> 5. Delete help and features nodes. (right clicked on these items)
> 6. Check java memory usage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
