Hi nanook!
A memory leak in a program means simply that the program allocates blocks of memory from the common memory pool shared by all your active software and forgets to return some of those blocks back to the pool when discarding them. If the program is constantly active (like Morpheus) even minor leaks add up quickly, robbing the system eventually from all free memory. The cure is to shut down and restart the program periodically. This is enough on more robust operating systems (WinNT, Win2000) where each active program runs in its own memory space and cannot usually f/u other running programs. On low-end systems (Win95, Win98) you better reboot your computer to resume all discarded memory.
A new version of Morpheus should come out in a few days. This will still be just an upgrade to the existing version but the good news is that there should be a control for max concurrent uploads. Non-existing upload controls have been one of the week points of Morpheus, discouraging generous full-library sharing. If the limiters work we might see a huge and sudden increase in the amount of shared material on Morpheus.
The more interesting 'New Morpheus' - a totally revamped client as MC likes to put it (no details given or publicly discussed) - is probably still months away from now.
- tg
