aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Worse than a crash.....aMule won't go away  (Read 2363 times)

lind15213

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
Worse than a crash.....aMule won't go away
« on: December 20, 2008, 12:07:12 AM »

Lately I've started having an issue where aMule 2.2.1 for OSX will stop responding, and then won't go away when I try to Force Quit. I've even tried using the Terminal to do "kill <pid>" and "kill -9 <pid>" (sending the TERM and KILL signals, respectively), but the program just won't go away. The ps program lists its status as " E" (that's space,E), which according to the man page means it's *trying* to exit.....just not being successful in doing so.

This prevents me from restarting my computer normally. And thanks to an unrelated problem, force-restarting is not something I want to do more than I have to.

Is there any kind of workaround for this, and is it a known problem? I'm on a TiBook G4 running OSX 10.4.11 (PowerPC).

This is in addition to the GUI just being generally slow to respond all too often (10-60 seconds between clicks and visual responses)----I've experienced that enough to know the difference. It's really frozen completely when this happens.
Logged

lfroen

  • Guest
Re: Worse than a crash.....aMule won't go away
« Reply #1 on: December 20, 2008, 10:05:09 AM »

When "kill -9" doesn't work - problem is not in application. Usually it means that application is waiting for syscall, which in turn blocked on some internal mutex/spinlock.
Logged