memory dumping

[DoKeR]

Can anybod say me why Geiss was to lazy to correctly clean memory while program- Milkdrop ending?
Well, i start my computer and i have 190 mb free
i start milkdrop first time, and a heve only 150 mb
2nd time i have 110 mb, 3rd 70, 4th 30, 5th 0-1,6th can't event initialize D3D!

[Illusion]

Firstly, it's not really very fair to call Geiss lazy, he must have put hundreds of hours of work into this plugin, so I don't think you should criticise him unless you can make a better plugin yourself.

Anyway... do you mean 190MB hard drive space, or the amount of RAM / system resources that you have free? There is no reason why it should be "losing" space on your hard drive, unless MD is using it as a swap file. You might want to delete / burn some stuff if that is the case, having 190MB free is not really a lot, especially considering that systems now come with 40GB or 60GB hard drives. It shouldn't really be too much of a problem though, because when you close Milkdrop I don't think there should be any problems. If you meant RAM / system resources, it probably just means you have a memory leak somewhere, so not sure what you can do about that. Usually failing to initialise Direct3D only causes problems for me when all my system resources are used up.

Well, there's my take on it, if I have understood wrong please explain it again and hppefully I or someone else on the boards will try to help you out.

[Ultima]

If you're running Win 95, 98, or ME... well that's your problem. These OS's lose memory like they have ulzheimer's, regardless of what programs you run. Get Win 2K, or some people like XP. I run MilkDrop all the time and never lose a byte of available RAM.
Ultima

[PigeonGB]

While I have decided that it is likely to leak memory, Windows 98 works fine for me until I run Winamp or MusicMatch to play my MP3s.
If anything, I am trying to figure out if it is my sound card drivers (SB Live! Value) or something else entirely.
Here is why I don't just want to get a new OS.
Running Windows Media Player with my winamp playlist can run all night without much, if any, problems with memory.
AOL Instant Messenger runs all night with no problems with memory.
I have a few programs running together all night with no issues with memory.
When I run Winamp (or Musicmatch) by itself, playing my playlist all night, after a few hours, hundreds of MB of memory are allocated and are not released even after I close it.

Now I have found that minimizing and restoring windows in my taskbar causes memory leaks, but as I can run Winamp by itself without touching the computer, I can see it is a separate issue.

Playing MP3s with anything other than Windows Media Player (and an older version at that: Pre-7.0) causes massive memory leakage.
So it is not Win98 per se, but something that Windows Media Player doesn't use that Winamp and Musicmatch do use.
If it is a difference in API calls used in the applications, then maybe it is the drivers or something else, but it is not the OS in itself.

[Krash]

Still sounds like the OS to me. I'm running WinXP pro (tweaked so it looks like a computer rather than a candy store, of course), and running milkdrop uses 500k of physical ram, which is reclaimed the instant I close milkdrop.

- Krash

[Ultima]

PigeonGB said...
So it is not Win98 per se, but something that Windows Media Player doesn't use that Winamp and Musicmatch do use.I can see what PigeonGB is saying, though. Some Win-API call that Winamp uses is buggy in Win98, but not in Win2K or WinXP.

On a separate note, I really don't see WinXP as a viable upgrade to Win2K. Besides it's hideous interface :igor: (which I agree with Krash, needs to be tweaked to make it bearable), I hate the registration scheme :down: , and also most of the "performance improvements" that IMO slow it down in the long run. So I'm really hoping Linux will become a better desktop OS in the next year or two. Guess I wandered a bit off-topic.... :D
Ultima

[PigeonGB]

Windows98SE does not do a good job with memory deallocation, I agree.
But my point is that Windows Media Player does not have as noticeably huge of a problem with memory leaking when it plays the same music list as Winamp does.
With Winamp, after an hour or two, I might have 50-100MB allocated, whereas in Windows Media Player, I might have 2-8MB allocated.
Closing Winamp, the memory only deallocates about whatever it takes to have Winamp open, but the 50-100MB roughly stays allocated.
I close Windows Media Player, the 2-8MB are deallocated, and even if they aren't, it is not as huge of a problem as over 100 or, when I play for more than a couple of hours, 500MB.