[MAGNOLIA-1580] memory: potential memory leak when deleting node Created: 09/Jun/07  Updated: 23/Jun/14  Resolved: 23/Jun/14

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Marcin Oscieck Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows XP, 2003


Attachments: Text File tomcat.log    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Philipp Bracher [ 13/Jun/07 ]

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

Generated at Mon Feb 12 03:28:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.