0.7.11 Intermittently Quits [OS X]

[shypike]

Keep testing, while I look for a possible solution.
That might take a while, because I cannot test any solution.
Neither one of my two Apple systems have this problem.

[c_seed]

I had the same problem and Having read this this thread, I decided to test 0.7.10 only to discover that it is suffering from the same problem. I have now downgraded to 0.7.9 and will report what happens.

My OS version is 10.8.2 running on a 2.3 ghz system with 16gb RAM.

[shypike]

Try the Lion version too.

[c_seed]

0.7.9 has been running without quitting since my last post. I will keep you informed.

[shypike]

That's 0.7.9 MountainLion build?

[bhive01]

I've been running 0.7.11 Lion build for a few days now and no problems on 10.8.2. Clearly it's something with the Mountain Lion build. Perhaps it's specific to some hardware?

I'm running on a MBA 13-inch Mid-2011.

[shypike]

It's something with the ML build and with the hardware, the combination at least.

[c_seed]

I am running the 0.7.9 ML build on a Mac Mini 2.3 Ghz i7 with 16 GB RAM and SSD for a startup disk. All the media gets dumped onto an external 8TB Hardware RAID5 (Lian Li EX503 enclosure). Hope this info helps you figure it out. If I can help in any way, let me know.

[shypike]

It's not likely to be defective hardware, but just a combination of drivers, OS, amount of memory etc.
I have the latest i7 iMac and a 2010 dual-core mini, both with ample memory.
Neither one exhibits this problem...

The difference between the Lion and MLion build is that they use different versions of Python.
It would be impossible to implement the stay-awake option when using the Lion build.
I will look into this further, but it may very well be a long search, especially since I cannot reproduce the problem.

[syd3n]

I am experiencing a similar problem using:
OS - OS X 10.8.3
SABnzbd - 0.7.11

SABnzbd keeps crashing very frequently for me. I feel the longest I've seen it run without crashing is maybe 2 hours. This is the first time I have installed and started running SABnzbd on this machine. It is a new machine...but obviously I have have a ton of other stuff installed on it already so I can't call it a fresh install.

I realize that the suggested solution is to use an older version, but I just wanted to ask if my current install's crash reports would be helpful in anyway. What is the recommended method for submitting the crash reports?

[shypike]

I realize that the suggested solution is to use an older version

No, it's using the Lion build in the same DMG.
I don't need any more crash reports, because they contain no useful information.
Next week or so, I'll have a new build available, produced with an older build environment.
(Because that's about the only cause I can think off.)

[syd3n]

thanks for the clarification!

[syd3n]

Even the Lion version is crashing for me. I just installed over the previous version.

Will appreciate any further suggestions.

[bhive01]

Yeah, I've had issues with 0.7.11 Lion version running on 10.8.3 (was 10.8.2 last time) the last few weeks. It's usually linked with when my MBA goes to sleep and then wakes back up. I shut the lid and when I open it and log back in, it's not running anymore. It doesn't always happen though so it's really hard to pin down. I've closed and opened my Air 10 times this morning after restarting SABnzbd and it's still running.

[Zytech]

Same problem here. If I remember correct it occurred also with 0.7.10.

I am running sabnzbd on 10.8.3 Mac Mini 2011

Here is the crash log:

system.log
Mar 28 21:50:20 Server com.apple.launchd.peruser.501[145] ([0x0-0x20020].org.sabnzbd.team[285]): Job appears to have crashed: Bus error: 10
Mar 28 21:50:21 Server.local ReportCrash[2679]: Saved crash report for SABnzbd[285] version 0.7.11 (0.0.0) to /Users/User/Library/Logs/DiagnosticReports/SABnzbd_2013-03-28-215021_Server.crash

diagnostic report:
via PasteBin ( too big for forum.. )
http://pastebin.com/Uj0gZpSY