SABnzbd Forums

It crashed again with all the defaults. I am running in the CLI now, hopefully it will show something.

I guess I have to put my foot in my mouth, I swear I didn't see this before:

/usr/bin/sabnzbd on OSX?
Ah, right another Thread hijacker. I'm splitting this subject.
(Damn phpBB doesn't split right...)

Sorry for hijacking the thread. Thanks for the help. I hope I get this figured out.

Such crashes usually mean one of two things.
1) For some reason the process or the system ran out of memory.
2) The Python runtime or one of the modules (yEnc, OpenSSL) crashed due to a bug.
In the latter case there's not much we can do.
Bugs in SABnzbd's own code can cause lots of problems, but not segmentation faults.

I do notice that there are lot of instances of SABnzbd when I run htop. It may be a memory leak.

brad0383 wrote:I do notice that there are lot of instances of SABnzbd when I run htop. It may be a memory leak.

Those aren't instances, those are threads. htop shows multiple threads as separate lines. So no, this isn't a memory leak.

inpheaux wrote:

brad0383 wrote:I do notice that there are lot of instances of SABnzbd when I run htop. It may be a memory leak.

Those aren't instances, those are threads. htop shows multiple threads as separate lines. So no, this isn't a memory leak.

Ahhh, yes, I forgot about HTOP showing threaded processes and seperate lines.

It looks like this can be marked as solved. I had the incomplete download directory on my / partition and the completed downloads on my /home partition. If the download queue is larger than the available space in the incomplete directory it will crash even though the files are moved when they are complete. I changed the incomplete directory to my /home partition and everything is working fine.

May have spoken too soon. This is gonna make me pull my hair out!

Have you already run memtest86 for a few hours to see if your memory is 100% OK?

sander wrote:Have you already run memtest86 for a few hours to see if your memory is 100% OK?

That was a good idea. I ran memtest86, no errors. I hate to say, but I may have to try the "Micro$oft" fix and format the drive and start over.

brad0383 wrote:

sander wrote:Have you already run memtest86 for a few hours to see if your memory is 100% OK?

That was a good idea. I ran memtest86, no errors. I hate to say, but I may have to try the "Micro$oft" fix and format the drive and start over.

You could first try Ubuntu.

sander wrote:

brad0383 wrote:

sander wrote:Have you already run memtest86 for a few hours to see if your memory is 100% OK?

That was a good idea. I ran memtest86, no errors. I hate to say, but I may have to try the "Micro$oft" fix and format the drive and start over.

You could first try Ubuntu.

I have no interest in Ubuntu. I just came from there.

I just read on your FAQ's that python 2.7 is not supported. Is this true?