[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: |
|
| 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. Replicable |
| 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 |