Killing/Removing unneeded processes?
I am running Xubuntu 12.04 on some really old hardware. A 1.8Ghz Core2Duo with only 2GB RAM (maxed out). I can't even run google chrome with only 1 tab (website being random.org) and kazam screencaster (not even recording, just open) without chrome giving me the Jim's Dead screen because my system is out of memory.
I am curious if there are any background process's I can kill, for example I killed xfce4-volumned, which is for keyboard audio controls which my keyboard doesn't even have. That fee'd up some RAM but there are a ton of other process's that I am not sure what they do. When I run kazam to capture me playing shank 2, I kill dropbox app and many other process's just wondering if there's a guide for trimming down the fat.
I did change my swapiness to 10 which seemed to help at first BUT not it appears like I run out of memory way to fast being that I have 2GB of RAM.
Thanks for any help you can provide.
Re: Killing/Removing unneeded processes?
Dual core with 2G of ram is plenty for xubuntu. What's eating up your memory?
Re: Killing/Removing unneeded processes?
Xubuntu should normally only use about 150MB ram on startup, and I agree that your machine should run that OS without any problem; it should even be able to run vanilla Ubuntu with unity if you have the appropriate graphic card for 3D.
Something is obviously very wrong, so the top command suggested by lbjsb4 should show you what is using all your resources and give you some idea about what to do.
Re: Killing/Removing unneeded processes?
ok, will post the top output later after work. i am finding it very weird to run out of memory with only running kazam screencaster and google chrome with only 1 tab. it was rediculious that i couldn't even get 1 webpage to load, chrome said Jim's Dead or whatever when there's no memory for it.
I wonder if there's a memory leak within kazam cause it wasn't even recording, it was merely open that's all. I know when recording a 1280x720 window it will use a lot of resources.
thanks for the replies guys, will post up a top output later
Re: Killing/Removing unneeded processes?
here's when I rendering a video to h264 and aac audio, have chomr open with 4 or 5 tabs, skype, a terminal, some nautilus windows open and that's it. oh and dropbox running in background.https://lh4.googleusercontent.com/-v...k/s683/top.png
Re: Killing/Removing unneeded processes?
Quote:
Originally Posted by
dannyboy79
What's melt? The 4th process down (eg 17157) is using 137% CPU. Yikes!
Re: Killing/Removing unneeded processes?
Quote:
Originally Posted by
bab1
What's melt? The 4th process down (eg 17157) is using 137% CPU. Yikes!
melt is doing the rendering in kdenlive.
I don't understand how this output relates to your initial problem. You can run all this without any problem but not with the screencast software?
Can you show the output of top with just the screencast software running?
Re: Killing/Removing unneeded processes?
Quote:
Originally Posted by
omeomi
melt is doing the rendering in kdenlive.
I don't understand how this output relates to your initial problem. You can run all this without any problem but not with the screencast software?
Can you show the output of top with just the screencast software running?
sure, sorry about that. here's with kazam running and chrome with only 3 tabs running
https://lh3.googleusercontent.com/-3.../s688/top1.png
Re: Killing/Removing unneeded processes?
Quote:
Originally Posted by
dannyboy79
sure, sorry about that. here's with kazam running and chrome with only 3 tabs running
[I M G]h t t p s : //lh3.googleusercontent.com/-3Mm2eedpY1I/UP5uvkBSIVI/AAAAAAAABcA/Xz3OFA2Pp18/s688/top1.png[/ I M G]
That image of top shows you have kde processes as well. So this isn't a "pure" Xubuntu.
Re: Killing/Removing unneeded processes?
Quote:
Originally Posted by
dannyboy79
sure, sorry about that. here's with kazam running and chrome with only 3 tabs running
Do you get the same thing if you run a different browser than Chrome?
The weird thing is that Chrome is supposed to use one process per tab, yet I count at least 11 chrome processes in your output. So it might be a problem with Chrome running wild or something.