by CrashMonkey » Thu May 09, 2024 11:30 am
Agreed that memory leaks should be solved. Big part of the leaks are Within the tag-lookup. And then old items that you did stay in memory. When importing a big database for first time, you reach that memory 2gb+ within a few hours.
However i have send the full memory dumps to the dev's so they could analyze them in the past. But they where unwanted, and not looked at.
| Under normal useage, mine uses only about 200-250 mb.
Is that all 4 processes counted together, or per instance.
Hope you don't check the memory usage shown in task manager, as that shows a lower use then accutually is using, you should look at the Working Set(in Resource Manager), as that represents the usage of physical memory used.
So for me, just after startup:
MediaMonkeyEngine.exe taskmgr memory: 5,7 MB WorkingSet 26,4MB
MediaMonkeyEngine.exe taskmgr memory: 143,5 MB WorkingSet 238MB
MediaMonkeyEngine.exe taskmgr memory: 11,5 MB WorkingSet 39MB
MediaMonkey.exe taskmgr memory: 37,5 MB WorkingSet 148MB
Working set represents the usage of physical memory used. What is shown is taskmanager is virtual memory, and that is only a smaller part.
So for me after startup, 450+mb for all processes together. (but for hitting the limit you should look only look at 1 process. (because al 4 exe file can use there own set of memory))
When you do a memory dump, you can dump workingset, however you can't dump the partional virtual memory as that is incomplete.
That said, i can load a program(64bit) with 1mb memory use, shown in taskmanager, but uses 10gb in workingset, that is not shown in taskmanager under memory. So you hit the 4gb memory limit faster then, most people think.
Until windows 7 taskmanager used to show the workingset, but changed in win 8 with the improved memory optimalisations. So showing a lower memory usage, However with 32bit programming you need to think of that change, and look at working set instead to see if your getting hit by the limit.
Agreed that memory leaks should be solved. Big part of the leaks are Within the tag-lookup. And then old items that you did stay in memory. When importing a big database for first time, you reach that memory 2gb+ within a few hours.
However i have send the full memory dumps to the dev's so they could analyze them in the past. But they where unwanted, and not looked at.
| Under normal useage, mine uses only about 200-250 mb.
Is that all 4 processes counted together, or per instance.
Hope you don't check the memory usage shown in task manager, as that shows a lower use then accutually is using, you should look at the Working Set(in Resource Manager), as that represents the usage of physical memory used.
So for me, just after startup:
MediaMonkeyEngine.exe taskmgr memory: 5,7 MB WorkingSet 26,4MB
MediaMonkeyEngine.exe taskmgr memory: 143,5 MB WorkingSet 238MB
MediaMonkeyEngine.exe taskmgr memory: 11,5 MB WorkingSet 39MB
MediaMonkey.exe taskmgr memory: 37,5 MB WorkingSet 148MB
Working set represents the usage of physical memory used. What is shown is taskmanager is virtual memory, and that is only a smaller part.
So for me after startup, 450+mb for all processes together. (but for hitting the limit you should look only look at 1 process. (because al 4 exe file can use there own set of memory))
When you do a memory dump, you can dump workingset, however you can't dump the partional virtual memory as that is incomplete.
That said, i can load a program(64bit) with 1mb memory use, shown in taskmanager, but uses 10gb in workingset, that is not shown in taskmanager under memory. So you hit the 4gb memory limit faster then, most people think.
Until windows 7 taskmanager used to show the workingset, but changed in win 8 with the improved memory optimalisations. So showing a lower memory usage, However with 32bit programming you need to think of that change, and look at working set instead to see if your getting hit by the limit.