[CLOSED DUPLICATE] Exiting takes too long

[napilut]

Hi,

First of all, hello. My name is Jordi and I'm from Spain. Sorry about my poor English, I whish you can understand me.

I'm using the latest Transmission version (1.91) for Mac.
My system: MacBook 13", 2.4GHz (Intel), 4GB DD3, Mac OS Snow Leopard.

I have problems each time I try to close the Transmission application. The window closes itself good but the Dock icon still working with the label 'Saliendo' (I have the spanish version of it so I supose that the english message would be 'Exiting' ). However it never ends and I must force the application to close. Hence, when I start the application again, the application must check the files loosing too much time.

It doesn't happen every time I close the application, but it happen around the 75% of times.

If you need more information ask for it, I'll try to help you to solve this problem. I have no found any post about this issue.

Thank you.

Jordi

[napilut]

I have to wait too much time. For example, some days go I closed transmission before go to work at 8a.m., when I returned at 10p.m. Transmission still trying to close itself with the label 'Closing' over the dock icon. When it happens, if I open the 'Force exit' windows on Mac, Transmission application appears as 'No Responding' application. Hence, I must force to close it.

[Jordan]

Could you please try a nightly build of r10304 or higher from http://transmission.xpjets.com/ and see if the problem persists?

[Zirro]

Oh, I'm so glad I'm not alone about having this issue. It happens frequently, like the reporter says, about (50-)75% of the time and is starting to get a bit annoying, as I got quite many large torrents in my list now, and it has to do an "existing data check" the next time it is started, which takes at least two hours. It seems to occur more often when Transmission has been running for a while, rather than just for a short time. I am not exactly sure what Transmission is doing when it is "Quitting", but that seems to be where things goes wrong.

What might be even more troubling though, is that if you choose to restart your computer while still having Transmission running, this occurs:

1. You have Transmission running.
2. You choose to restart/shut off your computer (Mac).
3. Transmission tries to close, but runs into the problem.
4. You force quit Transmission.
5. The system proceed shutting itself off.
6. The OS is mostly turned off, but a blue background and a "spinning" cog, like the one seen at computer startup remains.
7. I've had it open for a maximum of five minutes, but it doesn't seem to go away (it probably remains "forever"), so I have to "force-quit" the computer, with the start-up button. This has now occured at least eight times.

I'd like to know if anyone can reproduce this.

Finally, I'll try downloading a nightly build in a few days, I am currently a bit busy.

Thank you!

[Zirro]

Now it occurred when I chose "Verify local data" from the menu, on a file where it seemed like I had lost 10 gigabytes of data from the last "crash" (The data was probably still there, Transmission just doesn't seem to find it again). Seems I'll be installing that nightly very soon, this can't go on any longer, I'm loosing too much time ;p

[Rave]

same trouble when quitting while there is active downloads or/and many seeding torrents.

[blsfalcon]

Hello Everyone.
I have the same problem.
After the update to version 1.91 i had the first crash of Mac OS Snow, since October.
I had to install version 1.83, and everything is working well now.


BF

[avpro]

Could you please try a nightly build of r10304 or higher from http://transmission.xpjets.com/ and see if the problem persists?

I can verify that this problem is not corrected by the latest build (1.91r10344). I have been complaining about this for months now (since v1.8) with no help forthcoming. I have 100% failure to quit every time I try to exit Transmission. No one here seems to understand what needing to force quit and (not responding) means in the Mac "Force Quit Applications" window. What it means is that the application has crashed! The last version which quits successfully on my system, after a "normal" wait, is v1.76. How about some attention to this issue... support guys?

[Jordan]

This thread, too, appears to be a duplicate of this thread. As such, I'm going to lock this thread too. Please don't keep starting duplicate threads, people. It makes the forums an unreadable, unsearchable mess. Please continue tihs conversation in the other thread.