I've finally figured out the cause of my KP's (it was due to a bad ACPI driver, of all random things). Now that things are 100% stable, of course Transmission works perfectly. I still think there should be some better crash / data handling, but I do understand why it's not a priority or looked into very much... since you'd need an unstable system to trigger the problems. For my own curiosity, I'd still love to know why Transmission basically starts torrents over after OS crashes; you would think it could recheck existing data, not just discard it all. But I guess my complaining part in it is over
zarkon55 wrote:I am also experiencing Kernel Panics. Transmission is the only app running, and this is on new MacBook Pro under the latest Snow Leopard.
Is there a fix for this?
The kernel panics are probably not caused by transmission (read previous posts).
Is there a better bittorrent client for Mac?
I'm ready to abandon this product...
No. Out of all of the Mac (and Linux) BT clients I've used, transmission is the most stable.
Been happening since the last few updates to the software. I can pull panic logs if there is anyone looking to troubleshoot.
-Walt
Version 1.x does not seems to have this issue on my MacBook Pro. However, version 2.01 and 2.03 almost always cause a panic.
On my other Mac (a Mini) it never crashes. (any version)
Here's a panic log:
Interval Since Last Panic Report: 469781 sec
Panics Since Last Report: 4
Anonymous UUID: 66670C72-74DE-4D74-9080-46F657FE1308
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10F569
Kernel version:
Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
Oh, BTW: I've never had a panic before using Transmission.... So in my mind it has to be Transmission doing it.
I've even re-started my Mac and run only Transmission, and not touched it, and it's panicked... Reverting to 1.x seems to fit it, or at least it's hasn't panicked so far back on the older version.
I've seen the panics connected on both the hard line (ethernet jack) and using airport. So it don't think it's that... I think Transmission is writing to memory in a location that is overwriting other stuff.
I does seem to happen on larger torrents, 500Mb+ with many seeds, but, I never even come close to maxing out my bandwidth. Other programs like Thoth and NZBDrop run at 3x the download speed over Transmission, so I don't think it has anything to do with bandwidth.
I don't remember seeing this issue with the 1.x version of Transmission. All the panics started with version 2.x
Again, it "feels" like a programing bug in the new software to me.
Been there, done that. (Before even searching this forum)
Ran extended Apple hardware test with no errors.
Verified hard drive.
Verified Permissions.
No other programs running, no new drivers or hardware.
I can reliably (every time) get it to KP with v2.03 on any file larger than about 300-400 megs. Seems to KP right around the 400Mb mark, but it varies slightly.
KPs on Airport connection or GB wired connection.
Reverting to v1.83 solves all KPs, and it's about 3X FASTER for total downloading speed !!!
I think this is a memory leak in the program causing this. Anybody have the source code?
-Walt
Last (2) Panics:
Interval Since Last Panic Report: 469781 sec
Panics Since Last Report: 4
Anonymous UUID: 66670C72-74DE-4D74-9080-46F657FE1308
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10F569
Kernel version:
Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
I did just now get it to KP with the older 1.83 version, but it still runs about 5X faster, so maybe it's just a factor of "how long" transmission is up and running?
I'm ready to find another app.
-Walt
Last KP:
Interval Since Last Panic Report: 479070 sec
Panics Since Last Report: 6
Anonymous UUID: 66670C72-74DE-4D74-9080-46F657FE1308
BSD process name corresponding to current thread: Transmission
Mac OS version:
10F569
Kernel version:
Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
zarkon55 wrote:I think this is a memory leak in the program causing this. Anybody have the source code?
Sounds to me like you don't know what a memory leak means. Source code is available, info on how to get it is on trac.transmissionbt.com. Please let me know if you notice any issues in the code.
I stand by my statement. I take it you're not actually willing to look at the code like you stated earlier - with your experience you could help us squash all of these issues you talk about.
I'll just point out that you came in here already decided it's a Transmission issue, and wouldn't consider anything else.
zarkon55 wrote:I does seem to happen on larger torrents, 500Mb+ with many seeds, but, I never even come close to maxing out my bandwidth. Other programs like Thoth and NZBDrop run at 3x the download speed over Transmission, so I don't think it has anything to do with bandwidth.
Even if you are not maxing out your bandwidth, you're still connected to alot of peers (to many connections can still slow down, even crash your system). All of your KP logs indicate that the cause of the KP is related to your airport/ethernet, and you said that you ran a hardware test and everything is normal, so you are probably overloading your system with to manny connections. Try lowering your peer connections like livings124 asked.
zarkon55 wrote:That's funny. I've been programming for 30 years, so yeah, I do know what a memory leak is....
Time to exit stage right, I've brought out the trolls.
-Goodbye.
If we were trolling, we would've told you to RTFM instead of trying to help you..
-Bye.
Last edited by r0n1n on Thu Jul 22, 2010 9:45 pm, edited 1 time in total.