Transmission causes leopard slow death

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
livings124
Transmission Developer
Posts: 3141
Joined: Fri Jan 13, 2006 8:08 pm

Re: Transmission causes leopard slow death

Post by livings124 »

jah: Yes, I was referring to your post. You have yet to acknowledge that your post basically says "The slowdown only occurs when another app is open and is fixed by closing that app." Posts like this make this problem extremely difficult to diagnose or pinpoint. Anyway, let's just continue with the regular leopard slow death discussion.
AtTheAsylum
Posts: 2
Joined: Thu Oct 30, 2008 12:21 am

Re: Transmission causes leopard slow death

Post by AtTheAsylum »

Hi all,

I've been following this thread for a while and can maybe offer some useful information.

This may sound obvious, but I don't believe the problem is caused directly by Transmission but more by an unintended interaction between Transmission 1.34 and the OS-X 10.5.5 update.

My story: up until a few weeks back I had been running Transmission 1.34 on an iMac running OS-X 10.5.4 without any issues whatsoever. Within the space of one week I applied the 10.5.5 update and then replaced my machines existing 2GB of memory with 4GB (ie: removed existing modules and replaced them with new ones). Less than a day after upgrading the memory I experienced the problems described here (machine hangs and has to be hard restarted). Initially I tried uninstalling anything that puts items into the menu bar since the spinning beach ball would usually appear there first. Another symptom was that the clock in the menu bar would stop. However, this didn't make any difference and the problem continued.

I then suspected the new memory, but after switching back in the old modules and observing the problem reoccur, I discarded this theory. At this stage I still did not suspect Transmission.

My next step was more drastic. I reinstalled the OS and patched back up to 10.5.4. I then reinstalled all my applications, including Transmission and those programs that place items in the menu bar. I ran with this configuration for a few days, using Transmission as I normally would, without any issues. This made me suspect that my initial application of the 10.5.5 patch had been faulty in some way. I then reapplied 10.5.5, restarted and watched to see what would happen. Within an hour the problems reoccurred with exactly the same symptoms as before. I was quite concerned at this stage and suspected that perhaps I had a hardware issue (new memory?) that only surfaced in 10.5.5. I still did not suspect Transmission. I then visited this forum and started to read this thread - something I should have done earlier :(

I uninstalled Transmission and installed Vuze and the problem went away. I then installed Transmission 1.22 and the problem did not reoccur.

So, in summary:
- OS-X 10.5.4 & Transmission 1.34 - Works.
- OS-X 10.5.5 & Transmission 1.34 - Problems occur.
- OS-X 10.5.5 & Transmission 1.22 - Works.
- OS-X 10.5.5 & other torrent clients - Works.

This above I can confirm after clean OS installs and patch applications.

My theory (probably obvious and if so I apologize) - the OS-X 10.5.5 patch set changed something that Transmission relies on and this change causes the problems we are seeing. This may be harder than it sounds, but would it be possible to see what changed between 10.5.4 and 10.5.5 and correlate this with libraries etc that Transmission relies on to try to narrow down the cause?
lopoz
Posts: 15
Joined: Sun May 18, 2008 9:55 am

Re: Transmission causes leopard slow death

Post by lopoz »

@AtTheAsylum

please try the latest nightly. for me it seems to have fixed the problem.
kidmidnight
Posts: 62
Joined: Mon Dec 31, 2007 11:47 pm

Re: Transmission causes leopard slow death

Post by kidmidnight »

AtTheAsylum wrote:Hi all,

I've been following this thread for a while and can maybe offer some useful information.

This may sound obvious, but I don't believe the problem is caused directly by Transmission but more by an unintended interaction between Transmission 1.34 and the OS-X 10.5.5 update.

My story: up until a few weeks back I had been running Transmission 1.34 on an iMac running OS-X 10.5.4 without any issues whatsoever. Within the space of one week I applied the 10.5.5 update and then replaced my machines existing 2GB of memory with 4GB (ie: removed existing modules and replaced them with new ones). Less than a day after upgrading the memory I experienced the problems described here (machine hangs and has to be hard restarted). Initially I tried uninstalling anything that puts items into the menu bar since the spinning beach ball would usually appear there first. Another symptom was that the clock in the menu bar would stop. However, this didn't make any difference and the problem continued.

I then suspected the new memory, but after switching back in the old modules and observing the problem reoccur, I discarded this theory. At this stage I still did not suspect Transmission.

My next step was more drastic. I reinstalled the OS and patched back up to 10.5.4. I then reinstalled all my applications, including Transmission and those programs that place items in the menu bar. I ran with this configuration for a few days, using Transmission as I normally would, without any issues. This made me suspect that my initial application of the 10.5.5 patch had been faulty in some way. I then reapplied 10.5.5, restarted and watched to see what would happen. Within an hour the problems reoccurred with exactly the same symptoms as before. I was quite concerned at this stage and suspected that perhaps I had a hardware issue (new memory?) that only surfaced in 10.5.5. I still did not suspect Transmission. I then visited this forum and started to read this thread - something I should have done earlier :(

I uninstalled Transmission and installed Vuze and the problem went away. I then installed Transmission 1.22 and the problem did not reoccur.

So, in summary:
- OS-X 10.5.4 & Transmission 1.34 - Works.
- OS-X 10.5.5 & Transmission 1.34 - Problems occur.
- OS-X 10.5.5 & Transmission 1.22 - Works.
- OS-X 10.5.5 & other torrent clients - Works.

This above I can confirm after clean OS installs and patch applications.

My theory (probably obvious and if so I apologize) - the OS-X 10.5.5 patch set changed something that Transmission relies on and this change causes the problems we are seeing. This may be harder than it sounds, but would it be possible to see what changed between 10.5.4 and 10.5.5 and correlate this with libraries etc that Transmission relies on to try to narrow down the cause?


yeah....... someone hasnt read the thread. it happens to people with versions 1.22 (possibly earlier) and up with 10.5 anything. i had 10.53 up until a week ago and it still happened.

The only thing that keeps it from happening is when i reduce the number of torrents im downloading. If i keep it at 2 I'm fine, any more though and the slow death thing stands a chance of happening. I had gone for about a month with no slow death until last night when i got bold and tried to download 3 files. When i woke up this morning the slow death was in full effect. 1.22 10.5.5 few month old imac
Jordan
Transmission Developer
Posts: 2311
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: Transmission causes leopard slow death

Post by Jordan »

kidmidnight wrote:yeah....... someone hasnt read the thread. it happens to people with versions 1.22 (possibly earlier) and up with 10.5 anything. i had 10.53 up until a week ago and it still happened
There's no need to be rude. He posted a pretty detailed list of the behavior that he saw.
Jeby
Posts: 33
Joined: Sat Sep 02, 2006 3:16 pm
Location: Cusano Milanino - Milano - Italy

Re: Transmission causes leopard slow death

Post by Jeby »

+1 here. Yesterday i've got 4 freeze in 1 hour! But I use Transmission 1.34 Mac OS X 10.5.5 on a MBP (not unibody)....
In my case I think the problem is vmnet (a vmware kext) related, because before the crash I see a lot of vmnet message in console

for example:

Code: Select all

Oct 31 16:28:38 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:38 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:38 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:38 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:38 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:38 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:39 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:40 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:42 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:42 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:43 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:43 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:43 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:43 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:44 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:44 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:44 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:44 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:45 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:46 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:46 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:47 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:47 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:47 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:47 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:48 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:48 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:48 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:48 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:50 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:50 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:51 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:53 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:53 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:53 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:53 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:28:57 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:28:57 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:01 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:01 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:01 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:01 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:02 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:02 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:06 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:06 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:07 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:08 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:08 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:08 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:08 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:09 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:09 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:09 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:09 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:11 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:11 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:11 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:11 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:16 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:16 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:17 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:17 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:18 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:18 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
Oct 31 16:29:20 alu-mate kernel[0]: vmnet: Failed to deep copy mbuf: 12.
Oct 31 16:29:20 alu-mate kernel[0]: vmnet: bridge-en1: SendToVNet mbuf dup/copy failed: 12.
vmnet is a kernel background process, it is running always.

However I see that the crash is more frequent whe I'm downloading from a large number of peers, for example yesterday I was downloading Ubuntu.
AtTheAsylum
Posts: 2
Joined: Thu Oct 30, 2008 12:21 am

Re: Transmission causes leopard slow death

Post by AtTheAsylum »

Hi all,

As lopoz suggested, I tried the latest nightly build (134+ 7016 at the time) and it seems to have fixed the problem. First I tried 3 torrents, all downloading, and left them overnight. When they completed I set up 6 more (3 downloading, 3 queued), left the original 3 to seed and again left them overnight. They're still running and so far I've had no issues :)

My next step is to reinstall 1.34 (release version) to see if the problem reoccurs with the exact same set of torrents (I know ;) but I like to be thorough).

kidmidnight, I'm sorry I gave the impression that I hadn't read the entire thread (I had by the way). Looking back at my post I must admit I made it seem that I was ignoring the fact that others had had similar issues with 1.22. I was just trying to relate my own observations in a clear manner without cluttering the post with information that didn't relate to my own experiences. I thought it may be useful to someone, especially considering the clean OS install and patching I had done.
ROOOP1
Posts: 3
Joined: Tue Nov 04, 2008 11:39 am

Re: Transmission causes leopard slow death

Post by ROOOP1 »

ALSO SUFFER SLOW DEATH.... ONLY THING TO DO IS CUT THE BLOOD TO THE BRAIN. THIS HAS HAPPENED 4 OR SO TIME SINCE T WAS ACTIVATED. ONLY WHEN DOWN LOADING WITH SPEED LIMKT ON ? OTHER WISE 3 X 700M TORRENTS AT THE SAME TIME ALL OK. TESTING AS I WRITE THIS BACK WITH RESULTS SOON.
ROOOP1
Posts: 3
Joined: Tue Nov 04, 2008 11:39 am

Re: Transmission causes leopard slow death

Post by ROOOP1 »

FOUND THAT APPLYING AUTO SPEED LIMITER TOTALLY CASHED MY NETWORK CONNECTIONS. ALSO FOUND THAT VM WARE PROGRAM WAS GOING OUT OF CONTROL USING UP ALL THE SYSTEM RESOURCES ! MANAGED TO SHUT THE AFENDING VM WARE APPLICATION DOWN (AFTER SHUTING DOWN T) AND WHAT DO YOU KNOW ALLS OK. WELL NOT SO OK AS I HAVE PROGRAMS ON MV THAT I NEED TO USE, SO I WOULD LIKE IT IF THEY COULD RUN SIDE BY SIDE.
pea
Posts: 381
Joined: Tue Apr 17, 2007 11:02 pm
Location: estonia, earth

Re: Transmission causes leopard slow death

Post by pea »

umm.. ROOOP1, is your Caps Lock brocken?
Loa
Posts: 1
Joined: Sun Nov 09, 2008 3:33 pm

Re: Transmission causes leopard slow death

Post by Loa »

Hello,

I posted another support post regarding this issue without knowing that it was widespread as this.

I haven't read all 15 pages of them so I don't know if my experience has been shared by others: this leopard slow death only happens on my FileVaulted account. Never even once on my regular account. Mind you: the crash can "infect" this non-filvaulted account, but as long as I only have Transmission running on my non-filevaulted account, I never get the crash.

Hope this helps,

Loa
chemicalseb
Posts: 1
Joined: Mon Nov 10, 2008 11:19 am

Re: Transmission causes leopard slow death

Post by chemicalseb »

I've read pretty much every post so far in this thread and I thought I'd like to tell you what happened to me.
I have been using Transmission since this June and have updated to every new version as soon as they were available.
Transmission had ALWAYS been very reliable and fast and almost never crashed.
All this changed 2 days ago.

That is when I was doing a lot of encoding of dvds into mp4 and such. Plus I was downloading stuff on Transmission.
Then I started noticing that transmission was slower. I assumed it was because I was encoding things at the same time.
However, now that I am not encoding anything, Transmission will still crash. What happens is, I start downloading a torrent, the speed is quite mediocre now. It'll go up for a second and then go back down, and keep repeating this pattern. (all ports open etc). It won't go past 10kb/s. (when downloading from normal sites, my speeds are incredibly good). Then when I try to close Transmission, it will get stuck and won't go away from the tray.

If I open transmission without any torrent inside, it will close fine.

I save to OSX's regular "downloads" folder. I also have an external HD hooked up and tried transmission with the external HD on and off. No difference.

I REALLLY don't think that it's a network problem.
It's got to be related to RAM or disk cache or something like that.

However, I had been downloading torrents that contained a lot of files when this problem happened.
I shall test this with torrents that only have a few files in them.

But it's still very strange that it just started 2 days ago when it was working so well for the past 5 months.

Could transmission work fine until loading BIG torrents? and then something gets screwed up in OSX or something?
kidmidnight
Posts: 62
Joined: Mon Dec 31, 2007 11:47 pm

Re: Transmission causes leopard slow death

Post by kidmidnight »

that isnt the same problem
martin308
Posts: 10
Joined: Sat Sep 13, 2008 9:21 pm

Re: Transmission causes leopard slow death

Post by martin308 »

I noticed that there was a new version of transmission this morning, anyone tried to replicate the problem with it? Ill try this weekend
psykeeq
Posts: 5
Joined: Wed Sep 03, 2008 6:43 pm

Re: Transmission causes leopard slow death

Post by psykeeq »

So did anybody with this problem tried the latest version 1.40? Im using azureus at the moment witch works fine but I want to switch back to transmission and im only gonna do it when this bug is solved.
Post Reply