* europax@home.com <europax@home.com>:

I found that the latest Realplayer linux beta gradually uses up all of memory and then all of swap until it locks up my computer to where a hard reset is needed. I remember some others having various problems, but I don't remember this one being listed. Its a very slow process, so I wouldn't leave a computer running unattended like I did listening to music :) It takes about 30 minutes or more on my computer. I send them a bug report.

Hmm, I have used the latest realplayer several times for well over 30 minutes straight and this (thankfully) hasn't happened. The symptom you mention though I have had happen to some degree -- never quite so bad that I had to do a hard reset though. It happened very recently with Emacs using W3; it used to with Netscape; it almost did with gqview. This is probably the most annoying thing that happens in Linux (it happened even more often in Windows though, and with a smattering of general page faults and a good ol' BSOD thrown in for good measure ;-). Then again, my 32 megs of ram probably doesn't help much... Can't the operating system defend itself against this in some way? I don't run as root, so it seems that I shouldn't be able to use all the resources and essentialy freeze the computer. Maybe there is a feature I am unaware of? <david> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/