View Full Version : Torrent Software Crash
I have had Transmission 1.4 crash on me several times.
It originally happened when I was using uTorrent beta so I figured it was just an unreliable build no big deal. Deleted all torrent data and started fresh w/ transmission. Again, fails. Deleted that data because I thought it was of the fact that I was d/l to my external. Reloaded again and boom, crashes. So I logged out and restarted (w/o reloading torrents) we are running strong for the past...3 minutes.
Any ideas? It seems to really bog down my computers performance too. (not the internet but the actual me doing things.
lanceomni
12-18-2008, 12:46 PM
Does it freeze, crash to desktop or restart?
Does it freeze, crash to desktop or restart?
It freezes.
lanceomni
12-19-2008, 01:08 PM
It sounds like a memory issue.
I was a bit baffled by my issue as I didn't think that downloading torrents with transmission would be related to a memory problem. I opened Activity Monitor/System Memory tab and started up my torrents. I watch the memory usage and noticed that It would slowly start filling available memory. The system would consistently freeze when I passed 3.6GB. I then opened a large document in Photoshop and did some heavy work with it and was able to replicate the freeze.
Test to see if this is the problem.
Use the boot-flag maxmem=2048 on startup. This will limit the memory that OSX uses to 2GB. Run your torrents as usual and see if you still get the freezes.
-The fix
Slashack over on insanely mac posted some modified 64bit kexts which fixed the problem for me. We are not using the same chipset so you will have to see if one of his works for you. http://forum.insanelymac.com/index.php?showtopic=127611
-Using maxmem as a fix
Try the maxmem flag on boot and if it works add it to com.apple.Boot.plist (located in /Library/Preferences/SystemConfiguration/) The syntax goes something like this:
<key>Kernel Flags</key>
<string>maxmem=****</string>
Replacing **** with the amount of memory to use. Many people have reported 3456 (3.38gb) works well. I have pushed mine to 3584 (3.5gb) and have not been able to make it freeze.
Network related freezes
Most of the time people with your symptoms have the problem with memory. I have heard others who have had issues with their lan drivers. Id use maxmem to test for the above first.
i'm currently using 4.8gb of my ram and there is no freeze...I have 8gb of ram. I could try opening up some fcp and some adobe suite and see if that pushes me to any where near 8gb. What is the "stock" maxmem input?
lanceomni
12-19-2008, 07:25 PM
There is no stock value. For most Ive seen, it seems to start giving problem around 3.2-3.5GB.
Id just open up Activity Monitor's Memory tab and compile some video... maybe open every program in your apps folder and see how high you can push it. I had a hard time getting up to 4GB. Ill have to do some research on an app that will simulate this. I am sure there is something out there.
So as of now at 4.8GB your stable?
actually burning a dvd right now and rendering movie in Final Cut and running at like 5.6gb and extremely stable
lanceomni
12-19-2008, 08:23 PM
I have not had a chance to do any extensive editing in FCP on my AMD rig. Has it worked well for you in terms of performance? I use a PPC dual 2.4Ghz Proc & 4GB of memory at work and from the little I have done on my AMD rig it seems my rig outperforms. I have been pretty impressed so far.
Absolutley amazing. I'm pretty sure I'm using the same computer at my work as you are and my Quad Phenom and the 8gb of ram is incredible. I run the whole FC Studio and it runs amazing on here. I haven't had one issue with a freeze or lock up while in FC. Just amazing.
lanceomni
12-20-2008, 11:05 PM
Let me backup a bit. Are you using maxmem or those modified 64bit kexts? Or have you corrected the freezing issue some other way?
i dont know why it would freeze. I'm not using 64 but kexts or maxmem, but i can use way more than 3gb of ram w/o my computer locking up. I still havent found out why my lockup happend w/ my torrent software.
PS, what is the 64bit kext? Because when I try booting for 64 bit flag w/ amd and new kernel, it wont load my os x.
lanceomni
12-21-2008, 02:30 PM
There is an issue with AppleNForceATA and other ATA kexts in that they are written using 32bit addresses. This causes problems with using ~ 3gb - 3.5gb of memory. The fix listed in my signature comes from Slashack. This person modified the kext using 64bit addresses which solved the problem for me. In your case though if its not broken don't fix it.
OSX can run in 64bit mode when this is offered by the processor. It may however cause problems running PPC applications through rossetta. Some applications can take advantage of 64bit but most of the kexts (drivers) out their are not 64bit. OSX 10.6 "snow leopard" should be a big jump in the right direction. I believe we will see 64bit kexts across the board and hopefully more 64bit software support
Im not sure why you are having problems with enabling 64bit with the new kernel.