Page 1 of 1
Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBUS)
Posted: November 12th, 2013, 9:26 pm
by sumocomputers
Sab v0.7.16
Mac OSX 10.8.5 on Mac Mini i5 with 8GB
Python 2.7.5
Also have Sickbeard & Couchpotato installed
I tried to search, but most of the errors are not quite the same as mine, or are very old, so I start a new one.
Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBUS). It does this randomly, but seems to be when downloading large files (like maybe larger than 10GB total?), just a guess, but when idle, it never seems to shut down.
Crash log is here, hopefully it is enough to get an idea of what I can do for troubleshoot:
http://pastebin.com/QhiMy9NT
In the meantime I upgraded Python to 2.7.6 just to see if this might make a difference, since the logs showed a lot of python (sorry, I really don't know what the logs are telling me).
Thanks,
Chris
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 13th, 2013, 1:04 am
by ernine
It's crashing in yEnc decoding (converting a text-based Usenet post back to binary) which unfortunately suggests a hardware or system problem, especially if it's happening quite frequently and not just on a particular file.
In any case it's outside sabnzbd itself, in an external library.
Thread 18 Crashed:
0 _yenc.so 0x01a87942 decode_string + 338
1 org.python.python 0x0017990a PyCFunction_Call + 98
2 org.python.python 0x001c7ef4 PyEval_EvalFrameEx + 8182
3 org.python.python 0x001cbe37 0x10e000 + 777783
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 13th, 2013, 10:07 am
by sumocomputers
ernine wrote:It's crashing in yEnc decoding (converting a text-based Usenet post back to binary) which unfortunately suggests a hardware or system problem, especially if it's happening quite frequently and not just on a particular file.
In any case it's outside sabnzbd itself, in an external library.
Thread 18 Crashed:
0 _yenc.so 0x01a87942 decode_string + 338
1 org.python.python 0x0017990a PyCFunction_Call + 98
2 org.python.python 0x001c7ef4 PyEval_EvalFrameEx + 8182
3 org.python.python 0x001cbe37 0x10e000 + 777783
Currently, it does keep crashing on a particular download, which I assumed because it was large. Perhaps it is something weird with one of the rar parts?
You suggested a system or hardware problem. I have recently ran the extended Apple hardware test at BIOS level, and found no issues. Also ran repair disk permissions. The Python 2.7.6 update did not change the problem.
Any ideas on where I can start to troubleshoot? Can I look at the library where yEnc lives?
Thanks
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 13th, 2013, 11:32 am
by sumocomputers
OK, now that I know it is yEnc, I have some more info:
1. Even though I have Python 2.7.6 installed on the Mac, Sabnzbd is reporting 2.7.2. Is this OK?
2. Regarding yEnc, I found this discussion:
https://github.com/sabnzbd/sabnzbd/issues/68. I am going to enable "use_pickle" to see if it helps. What about removing the yEnc library? Seems drastic, and not sure how to properly uninstall or reinstall the yEnc library.
Thanks
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 14th, 2013, 9:46 am
by shypike
SABnzbd comes with its own Python runtimes.
yEnc is a challenge for some systems.
Removing the module will only have some effect on CPU load,
SABnzbd will still function properly.
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 14th, 2013, 11:26 am
by sumocomputers
OK, for the yEnc stuff, I will try removing "use_pickle", followed by removing the yEnc module.
But in the meantime, now I am seeing another type of crash, which appears not to be yEnc related:
Exception Type: EXC_CRASH (SIGABRT)
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Full Log:
http://pastebin.com/hcgvWC2V
I have no idea how to start troubleshooting, any help would be appreciated.
Re: Sabnzbd crashes on OSX 10.8.5 with EXC_BAD_ACCESS (SIGBU
Posted: November 14th, 2013, 11:35 am
by shypike
We've seen that one before too, unfortunately.
So far no solution, it seems to be a bug in Apple's Python implementation.