Originally posted by inthegray
i made the screenshot.
windows xp pro, 512mb ram, 1.8 mhz.
winampm 5.03a, no vis, classic skin, minimized, a lot of other stuff turned off, with very other few programs running. i readily admit, that screenshot was taken under VERY optimal conditions.
though the image IS doctored (i didn't touch the winamp mem usage), it was mainly done for humorous exaggeration, as evidenced by some of the other processes in the screenshot. it was meant to show the vast expanse between memory used in Winamp, and memory used in other media players.
my apologies if you felt that i was claiming that winamp ran like that with average use.
no prob, I understand now
Still, it seems my WA is using more resources than it should. Btw, I may have found a bug (not sure)
I already edited my post up there, but I'l say it again here, in a bit more understandable fashion.
Here's the deal:
I didn't know WA uses less memory when minimized (it doesn't, but I'll get to that in a minute), until Rellik posted his message. I immediately checked, and as it turns out, if you minimize wa, the memoryload is cut in half. I then continued work as usual, but after a while I was clicking away windows, and stumbled across the taskmanager. Surprise Surprise, who's number one (on CPU usage)? offcourse: winamp
But while almost clicking away the window, I suddenly saw that memory usage was up at about 12megs, but I knew that wa was minimized. So I checked:
It seems that when minimizing was does do something do reduce the ammount of memory it needs, but when it starts playing the next song, it reclaims all the memory it was using while maximized.
so in short:
Winamp only uses less memory when minimized for one song, after that, it uses just as much memory as it would when it was maximized.