[DCMEE-1795] Memory leak on study deletions Created: 06/Feb/12  Updated: 28/Nov/18  Resolved: 28/Nov/18

Status: Closed
Project: dcm4chee
Components: Deleter
Affects versions: dcm4chee-2.17.0
Fix versions: None

Type: Bug Priority: Minor
Reporter: Brendan Moloney Assignee: Gunter Zeilinger
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified
Environment:

Linux (Debian 6), mysql


Testing Assignee: Peter Heiles
Tracking Status:
Risk Analysis - Todo, Test Spec - ToReview, Test State - Not tested
Sprint:

 Description   

While performing testing I needed to delete all of the studies in the archive (about 9,000 studies total). I set it so that studies that had not been accessed for one hour would get deleted. I also set it to delete the studies from the database. Memory usage slowly grew as the deletions occurred until it hit the 4GB limit for the heap. Some studies are larger than average, but it seems like this should not affect memory usage during deletions. The server was not handling any other transactions at the time.



 Comments   
Comment by Brendan Moloney [ 21/Feb/12 ]

This issue seems to have some other root cause. The most likely candidate is transaction timeouts while trying to delete very large studies. See this forum topic for more information: http://forums.dcm4che.org/jiveforums/thread.jspa?threadID=4463&tstart=0

Generated at Wed Apr 24 09:34:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100251-rev:0a2056e15286310f4b5e220c64c9aafb1684da34.