Sabnzbd+ randomly quitting on OSX

[shypike]

I have rebuilt 0.6.15 with ActiveState's Python, so it should be more stable and have the top menu again.
Can you test this new version for stability?

Download from:
http://sourceforge.net/projects/sabnzbd ... 5-OSX-Alt/

[trooper]

Sure thing, I'll grab it now
The Leopard install is still up and running by the way, so looking very promising.

[trooper]

Installed no problems and the top menu is back.
I'll report back in a couple of days as to whether it is stable.

Thanks a lot!

[trooper]

...and this morning I come back to a crashed sab again

Same message as always in the console log, so it doesn't look like it it the apple python library causing it.
In fact checking the download history, nothing has been sent to sab at all since I installed the ActiveState variant, so all it has done is sit in the background idle and waiting.

Swapping back to the Leopard version to continue testing that is still stable.

[shypike]

Interesting.
Both 0.6.15 versions have been built with Python 2.7,
but one using Apple Python and one using ActiveState Python.
The Leopard version uses ActiveState version 2.6 (but which cannot display the top menu).
So maybe using Apple Python 2.6 is the solution.
I'll get back to you.

[moilejter]

Hi! I am also seeing this crashes, running 0.6.15 on OSX 10.7.3...

The most recent log in Console says:

Code: Select all

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.python.python                0x00000001008b6b7a PyMethod_Fini + 168
1   org.python.python                0x00000001008b5af1 PyInstance_New + 10105
2   org.python.python                0x000000010092762f PyEval_EvalFrameEx + 11997
3   org.python.python                0x000000010092acd8 PyEval_EvalCodeEx + 1996
4   org.python.python                0x000000010092ae6c PyEval_EvalCode + 341
5   org.python.python                0x0000000100927e0a PyEval_EvalFrameEx + 14008
6   org.python.python                0x000000010092acd8 PyEval_EvalCodeEx + 1996
7   org.python.python                0x00000001008c8abf PyClassMethod_New + 1378
8   org.python.python                0x00000001008a7d32 PyObject_Call + 97
9   org.python.python                0x00000001009285ec PyEval_EvalFrameEx + 16026
10  org.python.python                0x000000010092acd8 PyEval_EvalCodeEx + 1996
11  org.python.python                0x000000010092ae6c PyEval_EvalCode + 341
12  org.python.python                0x0000000100927e0a PyEval_EvalFrameEx + 14008
13  org.python.python                0x000000010092acd8 PyEval_EvalCodeEx + 1996
14  org.python.python                0x00000001008c8abf PyClassMethod_New + 1378
15  org.python.python                0x00000001008a7d32 PyObject_Call + 97
16  _objc.so                         0x00000001010bb087 0x10108b000 + 196743
17  org.python.python                0x00000001008a7d32 PyObject_Call + 97
18  org.python.python                0x0000000100927f63 PyEval_EvalFrameEx + 14353
19  org.python.python                0x000000010092acd8 PyEval_EvalCodeEx + 1996
20  org.python.python                0x00000001008c8abf PyClassMethod_New + 1378
21  org.python.python                0x00000001008a7d32 PyObject_Call + 97
22  _objc.so                         0x00000001010a1449 0x10108b000 + 91209
23  libffi.dylib                     0x00007fff84a0e7ea ffi_closure_unix64_inner + 510
24  libffi.dylib                     0x00007fff84a0dffe ffi_closure_unix64 + 70
25  com.apple.Foundation             0x00007fff85ec2f64 __NSFireTimer + 102
26  com.apple.CoreFoundation         0x00007fff84138c24 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20


... and it keeps going ...

I can mail you a few crash logs, if that would help ...

Moises

[shypike]

I can mail you a few crash logs, if that would help ...

Not really, crash reports are seldom informative except at reporting the obvious: that it crashes.

All I can say is that such crashes are reported by very few people, despite the fact that we
have a sizeable number of OSX users.
So far, I'm at a loss about what the cause could be.
These kind of crashes are typical for errors in Python and its libraries or (less common) hardware issues.
Actual bugs in the app show themselves in different ways.
I can try a build with an alternative Python version.

BTW: have you tried 0.7.0Beta3 yet?

[moilejter]

Hi!

Downloaded 0.7.0B3 a couple of nights ago, switched to it - and it crashed again, overnight... :-(
I have a version of Python that is built on top of Java (Jython), would it be possible to run sabnzbd on top of that, instead of a native python? Maybe the error message would be different, and would provide more clues...

Moises

[shypike]

No idea if Jython works.
But ActiveState's Python does work.

[moilejter]

Downloaded 0.7.0B3 a couple of nights ago, switched to it - and it crashed again, overnight... :-(
I have a version of Python that is built on top of Java (Jython), would it be possible to run sabnzbd on top of that, instead of a native python? Maybe the error message would be different, and would provide more clues...

Speaking of which:

• it looks like memory use for this version of a low lower than it was for the 0.6.x one - on my machine, it seems to have gone down by more than %30?
• I disabled "osx menu" in the config page, and restarted the app - and the crashes seem to have gone away ...

Moises

[shypike]

I cannot comment on the memory reduction.
We did take some measures, but Python is often hard to predict.

Your success with disabling the OSX-top-menu is a clue about stability issues.
We've had reports before from a few people who had more stability with
the Leopard version on Lion than with the actual Lion version.
The Leopard version's OSX menu doesn't work on Lion due to an incompatibility issue,
but the nett effect is that it's disabled.
The cause an be a straightforward bug in SABnzbd menu code, but possibly
also a specific OSX configuration. A bug in Apple's Python is also a possibility.
The crashes do happen on a small minority of systems, making it very hard
for us to reproduce the problem, which is the necessary first step to resolving.

Thanks for the info, it could very well narrow down the search for cause.

[moilejter]

Well - it lasted a lot longer this time, but eventually 0.7.3 crashed, too... The report for the thread that crashed:

Code: Select all

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
objc[66090]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib           0x00007fff8891867a mach_msg_trap + 10
1   libsystem_kernel.dylib           0x00007fff88917d71 mach_msg + 73
2   com.apple.CoreFoundation         0x00007fff841106fc __CFRunLoopServiceMachPort + 188
3   com.apple.CoreFoundation         0x00007fff84118e64 __CFRunLoopRun + 1204
4   com.apple.CoreFoundation         0x00007fff84118676 CFRunLoopRunSpecific + 230
5   com.apple.HIToolbox              0x00007fff8cc3c31f RunCurrentEventLoopInMode + 277
6   com.apple.HIToolbox              0x00007fff8cc435c9 ReceiveNextEventCommon + 355
7   com.apple.HIToolbox              0x00007fff8cc43456 BlockUntilNextEventMatchingListInMode + 62
8   com.apple.AppKit                 0x00007fff8d2a2f5d _DPSNextEvent + 659
9   com.apple.AppKit                 0x00007fff8d2a2861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
10  com.apple.AppKit                 0x00007fff8d29f19d -[NSApplication run] + 470
11  com.apple.AppKit                 0x00007fff8d51db88 NSApplicationMain + 867
12  _AppKit.so                       0x000000010405720f 0x104056000 + 4623
13  org.python.python                0x0000000102427d77 PyEval_EvalFrameEx + 13861
14  org.python.python                0x000000010242acd8 PyEval_EvalCodeEx + 1996
...


So maybe it is something inside the core Apple frameworks ...

Moises

[shypike]

Too bad, makes it again very hard to diagnose.
That it happens on few systems (at least as far as I know)
makes it next to impossible to fix.
Simply said: I don't even have a clue what to look for.
The place of the crash is levels below the programming level...

[sflatchkey]

This doesn't solve the problem, but at least I'd rather automate the restart so that I don't have to worry about the crashes...

Create ~/Library/LaunchAgents/org.sabnzbd.plist and put this into it:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>Label</key>
  <string>org.sabnzbd</string>
  <key>KeepAlive</key>
  <true/>
  <key>ProgramArguments</key>
  <array>
    <string>/Applications/SABnzbd.app/Contents/MacOS/SABnzbd</string>
  </array>
  <key>RunAtLoad</key>
  <true/>
</dict>
</plist>


Then run:

Code: Select all

launchctl load -w ~/Library/LaunchAgents/org.sabnzbd.plist


That'll auto start/restart SABnzbd for you. I suggest you disable the auto open browser. =)

[shypike]

Some people have successfully gained stability by disabling the OSX top menu icon.
It's in Config->Special (in 0.7.0 only).