Environment:deltacloud-core-1.0.0-4.fc17.noarch (though same issue with dc-core from git)
Memory used by deltacloudd process increases with time. After 12 hours, it's common it uses ~4G of virt memory and >1G of physical memory (only conductor's dbomatic script which periodically checks running instances every minute was running).
You can reproduce the memory leak by this simple script:
1000.times do |i|
Used memory will increase by >10M (both virt and physical). The problem is probably with lambda in check_capability usage in lib/deltacloud/collections/* files:
check_capability :for => lambda
if the lambda is replaced by true or other static value, the memory usage remains constant.
I see that in git the 'check_capability' call was replaced by 'set' call, this change has no influence on this problem.
Also it's weird that after starting deltacloudd, used memory is 233m/33m (virt/res), but after first request, used memory jumps to 776m/90m (virt/res) - this is far more than on Fedora 16, where used memory remains around 160m/50m.
|Field||Original Value||New Value|
|Assignee||Michal Fojtik [ mfojtik ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|12d 5h 20m||1||Ronelle Landy||13/Aug/12 15:53|