![]() Registered Member ![]()
|
I'm running Ubuntu 8.04, Firefox 3, Amarok 1.4.9.1 and Text Editor. Gnome is my display manager. My machine is a P4 with 512MB RAM and an Nvidia GeForce 5600. My network card is an Intel something or other.
I was editing several remote files over sftp using Text Editor, and I had several web pages open for previewing the edits. I had been working for at least 45 minutes when all of sudden I couldn't save my files in Text Editor anymore. I received some error saying Unknown Protocol Error (or something like that). I thought maybe my network connection timed out, so I reopened the remote folder and reopened the file I was working on. I'm not quite sure what happened from here, but all of sudden my system started to hang. It was still responding, but very slowly. The hard drive was spinning continuously. I tried to quit firefox, but it just hung up. While all this was happening, Amarok began skipping through whatever song was playing. I was actually streaming music from Magnatune, at the time. I couldn't really do anything, so I tried to switch over to a console login. I finally got to login from the console, did a quick ps -ef to see what was eating up the CPU, but I didn't see anything which jumped out at me. I ended up killing firefox and amarok, then switched back to Gnome because the hard drive stopped spinning. After closing any remaing apps, I rebooted. Now, I really have no clue as to which app caused the problem, but I did find this in my kern.log:
Does anyone know if this had anything to do with what happened to my system? I just ran Amarok and killed it, but I didn't see a new instance of this info in kern.log. Any help is appreciated. |
![]() Registered Member ![]()
|
This message says that your system ran out of memory (oom) and thus killed amarok.
I blieve the "Tainted" has nothing to do with Amarok, but just tries to state if your Kernel was tainted (e.g., whether you ran some non-GPL driver). I am not even sure if Amarok is the cause for the out of memory condition. It is possible that the Kernel chose Amarok to be killed to free some memory for any reason, but I am no expert here. |
![]() Moderator ![]()
|
it's also possible that your RAM is failing or corrupt, but I'd suspect out of memory first.
|
![]() KDE Developer ![]()
|
|
![]() Registered Member ![]()
|
Thanks for the replies --- especially, "Buy some more RAM."
![]() My hunch is Firefox caused the out of memory problem. I think I'll hold off on the RAM. Thanks, again. |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]