Sabnzbd+ randomly quitting on OSX

[trooper]

I've noticed this random quitting, myself. Today, I looked into it, and sabnzbd had crashed.
I will attaching the crash report to this posting, in case this helps. The top few lines of the crash report are these:

As an experiment, can you try to run SABnzbd in 32 bit mode (instead of the default 64bit mode)?
Stop SABnzbd.
Open a Terminal window (Programs->Utilities)
Type:
arch -i386 /Applications/SABnzbd.app/Contents/MacOS/SABnzbd
Enter

So far I haven't been able to crash SABnzbd on my mid-2010 miniMac.

Just an FYI, I tried this and if anything it made the crashes more frequent!

Still having the same random crashing problems, but my workaround is to have a calendar job that starts the service at 4am everyday, so it is never down for more than 24 hours, even if I am away for a few days.

[trooper]

As mentioned, I expect it is a crash in a library that sabnzbd uses that takes it down (such as yenc), rather than sabnzbd itself,

There's one easy way to check the yEnc library.
Just remove yenc.py and _yenc.pyd from the SABnzbd.app folder structure.
SABnzbd will fall back to equivalent (but slower) Python code for yEnc decoding.
If this action prevents further crashes then at least I will have a lead for further research.

Just had a look in the installed app 0.6.14.

No yEnc files included in the app folder structure...

[shypike]

You need to remove this file:
/Applications/SABnzbd.app/Contents/Resources/lib/python2.7/lib-dynload/_yenc.so

[trooper]

You need to remove this file:
/Applications/SABnzbd.app/Contents/Resources/lib/python2.7/lib-dynload/_yenc.so

Done. I'll report back if it crashes.

[trooper]

So far so good! No crashes since disabling yenc.

[shypike]

Did you see any download speed reduction?
Without the library, SABnzbd needs to do its own yEnc decoding, which uses more CPU time.

[trooper]

Not noticeable on this machine, but it's a pretty beefy one (i7 iMac).

[shypike]

Still, strange that it crashes on your system.
Was there any system in the crashes?
Large NZBs?

[trooper]

Nothing massive, a few at 10gb or so, but most were around the 1gb mark. It's much more likely to crash if the queue has a lot of items in it.

It's only 2 days in so far, I'll report back in a week if it has stayed up for that long

[shypike]

Please do.

[trooper]

Nope, didn't survive the night

Nothing untoward in the log, no error messages, nothing.

Last couple of lines are

Code: Select all

2012-02-26 21:45:59,927::INFO::[downloader:351] [email protected]:563: Initiating connection
2012-02-26 21:46:12,264::INFO::[downloader:539] Connecting [email protected]:563 finished

[shypike]

Can you try one more thing?
It has helped users of some embedded Linux systems.
There's a "hidden" option in the sabnzbd.ini file called "use_pickle", set it to 1.
For this you need to edit the sabnzbd.ini file when SABnzbd isn't running.
Here how to do this:
http://wiki.sabnzbd.org/configure-special

[trooper]

Done. Well I added the option and restarted, as there wasn't that option in the ini file already.

[shypike]

Wait, you're using 0.6.10.
You'll need to upgrade to 0.6.15 first.
Also, that might even resolve the crashing.

[trooper]

I'm not, i'm on 0.6.15

the .ini file in the location specified in the post doesn't have use_pickle

.ini file is labeled as version 19 at the top.

All i've done to upgrade is download the 0.6.15 img package, stop the old version (0.6.14) and install the new version over the top, opting to replace when it prompts. Should I need to do something extra?