bad hang on Os X 10.4

[robbie]

Since upgrading to 1.11, I get a blocking issue after Transmission has run for a long time (a day or so, usually). I'm not certain this is transmission's problem, but I think it is.

What happens is: Transmission will fail to close. Every other app will exit when I try to close them, but transmission will not close even with a force quit. A look at the process shows it is a child process of:

60 1 ?? Ss 1:47.68 /System/Library/Frameworks/ApplicationServices?.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer -daemon

, and will list it something like:

1240 60 ?? E 1:0.0 (Transmission)

So it is failing to exit. Even a "sudo kill -9 1240" can't kill it.

Usually I discover this problem because of some other weird system error: I've had command+control+tab not work to indent text in textMate ... I've had Finder fail to open a new window. I go around looking at the other apps, generally closing things out, and find transmission, every time it is transmission, failing to close. I've done a full virus scan and have up to date virus software, repaired disk permissions, verified my disks, and I keep a fairly clean system with mainMenu and appDelete.

Since all the other applications can close out easily, and this never happened before I got the latest transmission, I think it is likely a Transmission bug.

[livings124]

Is there anything in Console.app. Do you get a crash report? Have you tried a nightly build? Right now there isn't even enough info to be certain it's a Transmission issue.

[livings124]

Closing so that the op knows to respond.