by Owyn » Fri Apr 18, 2008 6:36 am
Noticed that there can be long delays between network going idle for an episode download and the "1 track to be tagged" message appearing.
During this period VM Size for MediaMonkey.exe balloons by 100+MB.
This memory pressure can cause (on my admittedly small memory system) failures in other concurrent downloads depending on what else is also active, e.g. FF2. I have got in the habit of monitoring the process and killing firefox.exe if I see total commit growing too large.
IMHO, one advantage of testing on an older system is that it can surface problems that can be masked by lots of resources.
Noticed that there can be long delays between network going idle for an episode download and the "1 track to be tagged" message appearing.
During this period VM Size for MediaMonkey.exe balloons by 100+MB.
This memory pressure can cause (on my admittedly small memory system) failures in other concurrent downloads depending on what else is also active, e.g. FF2. I have got in the habit of monitoring the process and killing firefox.exe if I see total commit growing too large.
IMHO, one advantage of testing on an older system is that it can surface problems that can be masked by lots of resources.