Transmission causes leopard slow death

[runsnbunsn]

Hi!

Just tried nightly from yesterday night and as i can say now i doesn't help

when the global max. connection is 250, leopard dies instant death (about 10-30 minutes)
right now running it with 120 and it works (for an hour now), we will see

This problem is really weird, this weekend i friend of mine payed me a visit with his macbook, and used transmission over my network and it works fine on his machine, even if max. connections are 300!

One thing i noticed when Transmission killed the Leopard and i do a restart, the Mac startsound does not play anymore, until i restart a few times without running Transmission
Anybody else noticed this?

[Jordan]

Hi!

Just tried nightly from yesterday night and as i can say now i doesn't help

when the global max. connection is 250, leopard dies instant death (about 10-30 minutes)

Does CrashReporter generate a freeze report for this period?

[tempel]

Does CrashReporter generate a freeze report for this period?

Of course not. CrashReporter only records app crashes, but a system freeze is something totally different.

As I've explained, it's only the network stack that's dead, causing all apps that use sockets or whatever for comms are stalling. Forcing the Mac to sleep and then awaken it again usually helps - this shows that no crashing happens, hence no crash report.

Please read my comments on the previous page of this thread.

[joenp]

Thank god for this bug, I thought my iMac was dying!
I can still reproduce this in 1.34 build 6939, even with just one active torrent and speed limit of 200kb/sec. I'm switching to an earlier version of Transmission until this bug is fixed.

[runsnbunsn]

Hi again!

I finally got Transmission running stable for hours with 500 max. connections now!!

The Problem was a "User"-Bug, here is what I did.

I had activated the option for "Automatically Map Port" in the Preferences but also done a manual Portforwarding on my Router, when I disabled the option it worked just fine!
So i just stayed with manual Port forwarding and Transmission runs like before!
Hope this helps anybody!

[Jordan]

Thank god for this bug

Glad to be of service

[tempel]

Somemone added an interesting detail to the bug report:

VMware's added network interfaces or its NAT daemon might be part of the cause (http://trac.transmissionbt.com/ticket/1201)

What about others having this problem: Have you installed vmware as well?

I do (and I'm seeing the problem)!

In any case: Even if it's not caused by vmware (but only helping to indicate the problem better), the mentioned "mbuf starvation" is right on track with my findings on the dying network stack.

[martin308]

it's happening on my powermac g5 so definetly no vmware for me

[smswanie]

I thought I was going crazy (or my HD was dying). I've also had this issue off an on lately.

On my iMac, it was completely freezing the system with ~10 torrents running, but ~8 of them had been running for a long time with no issue. After about 3 freezes (all within 5 mins or starting Transmission), I trashed the preferences files and setup Transmission again. I have Automatically Map Port on on this computer.

On my MacBook Pro, it makes the HD sounds like it's seeking and dying and forces me to hard shut down. I'm using the nightly on this one and seems to be doing it with only 1 torrent running. This machine doesn't have the Map Port option.

Can anyone suggest a version of Transmission that doesn't do this in the mean time?

Also: Transmission HATES quitting. On any machine. Even after stopping the torrent and removing it, it hangs forever, sometimes causing the freeze.

[marioestrada]

With Transmission 1.22 I havent been experiencing this bug

[stephenr]

Hi,

First off - I haven't read all 13 pages of this thread, so please don't shoot me if I'm asking about something thats been said 8 pages before!

More importantly though. I have a Dual 2Ghz G5 PowerMac running OSX 10.5.5 & Transmission 1.34, and it exhibits the behaviour described. Generally it takes a few hours for the issue to rear its ugly little head, but if there is anything I can do to help solve this issue please let me know!

Cheers

Stephen

[runsnbunsn]

did anyone try removing the automatically map port checkbox and forwarding the port manually?

it worked for me and i tried many other things before which didnt work
and i dont have vmware installed

[stricken]

did anyone try removing the automatically map port checkbox and forwarding the port manually?

it worked for me and i tried many other things before which didnt work
and i dont have vmware installed

Yeah, I had that same option enabled, while also forwarding the port manually. I disabled it earlier today. It just froze OS X. Transmission wasn't downloading anything at the time, I have it's max download and upload rate set to 0 between 10am and 2am (my ISP's "off-peak" time). I also only have 4 torrents sitting in the queue, each around the 350mb mark.

*shrug* I'll try the latest nightly build now.

[DaniB]

I have tried turning off automatic port forwarding with the latest nightly build (6955) and this problem still remains. When I left my laptop with Transmission and some torrents active OS X had 2.5 gb of free ram. After one evening Transmission had eaten up everyting and only 10 mb was left. This is a serious issue and it renders Transmission almost totally useless. It's no solution to have to run iFreemem all the time. This behavior is unprecedented for a Mac app. No other app does this in Leopard. What are the developers doing to solve this situation?

[tempel]

Don't forget that this is a free app, by voluntary developers. Apparently they have a hard time figuring out what's going wrong here.