[AOM 0.5.1-4] stuck with 100% CPU usage [FIXED]
[AOM 0.5.1-4] stuck with 100% CPU usage [FIXED]
Not sure what's going on, but my client is now stuck every time I start it at the same part, namely at "converting and saving new anime title data".
The CPU usage remains at 100%, and I have to kill the client using task manager.
I tried to erase all files in my kowai folder, except for the local ones.
When the client restart, it downloads ok all the information, but is stuck again at the same part.
It was working fine until two days ago, and I didn't change anything in my configuration, so I'm clueless about how to fix it.
The CPU usage remains at 100%, and I have to kill the client using task manager.
I tried to erase all files in my kowai folder, except for the local ones.
When the client restart, it downloads ok all the information, but is stuck again at the same part.
It was working fine until two days ago, and I didn't change anything in my configuration, so I'm clueless about how to fix it.
-
- AniDB Staff
- Posts: 438
- Joined: Thu Apr 08, 2004 1:43 am
- Location: Portugal
Sounds like one of your harddrive disks is failing.shaman wrote:Ghm same here. It usually happens while browsing Know files section. I kill the proccess but usually it brings the whole system down (I'm using Windows 2000 on AMD with 1G RAM).
The thing that i have to reboot after using AOM really sux
AoM itself shouldn't have anything that can actually crash your system, sure it might use cpu but nothing in the program itself should cause trouble if you ctrl+alt+del it, rather it's something like reading from disk or tother hardware/software issues that causes this.
Ghm.... Well as I have noticed the system crashes cause after AOM crashes and it is killed other proccesses reach 100% one by one (e.g. notepad, iexplore, anypass were running while i was using AOM, when i killed AOM i switched to notepad and seconds later it also reached 100% CPU, the iexplore and finally explorer.exe ).
I don't know whether it's my hardware or AOM, but such weird stuff happens only when AOM is started and it yet happend only while browsing local files.
I don't know whether it's my hardware or AOM, but such weird stuff happens only when AOM is started and it yet happend only while browsing local files.