aMule Forum
English => aMule crashes => Topic started by: germ on February 11, 2006, 07:06:43 AM
-
aMule 2.1.0 works very well on my mac mini.
Unfortunately, every 2-3 days, aMule brings down the entire machine!
When I come home, the screen is black and the machine is on but unresponsive. I have to restart. One time there was a window saying the Mac OS X has unexpectedly quite (not just aMule, the whole OS).
I say this is aMule because when this happens aMule was always running, and I have had the computer now running for a week w/o aMule and I didn't get any crashes.
I hope I posted on the right forum....
-
What you are seeing is called a kernel panic. And there should be no way for an application to cause that. Basically, it indicates a bug in the kernel (or some kernel-level driver). Now it is possible that such bugs in the kernel are particularly sensitive to the behavior of certain applications but not others, but that doesn't mean it's the application's fault.
In the case of aMule, there are no reports of kernel panics from other users.
The most likely cause of kernel panics in Mac OS X is actually bad RAM. Check out this link (http://www.macintouch.com/badram01.html) for a lengthy discussion of the topic. If you added third-party RAM, try removing it to see if the kernel panics go away. If you bought from a reputable source, they should replace it free of charge.
There are other possible causes (hardware issues, misbehaving drivers, etc.), but aMule isn't one of them. Make sure to report the kernel panics to Apple (the OS should automatically offer to do this) and maybe bring the system in to an Apple Store to be checked out.
-
Thank you for the quickl reply.
I don't think this is a kernel panic (at least, it's not the standard kernel panic with the multi-lingual message that tells the user to restart the computer).
I am pretty sure I do not have a bad memory problem, as I have tested my memory expansion with memtest and found no issues. Also, my mini is extremely stable otherwise.
For the reasons stated in the first post, I strongly believe the crashes are caused be aMule, although I cannot prove it with 100% certainty.
There are no entries in the system logs related to these crashes (at least, not that I can easily find).
I realize that this is little useful information to go after the problem, but it's real...
Any suggestion on how to help identify the source of the problem?