Support Forum

In the Status window, can you switch the logging level to +Debug?
Then wait until this crash happens again, then we have the new logs.

After deselecting Check before downloading, did you re-add the jobs?
Doesn't work to just continue jobs already in the queue.

I honestly have no idea..

No, it's something with your unrar: It should say the path to your Unrar there instead of 'None'

Unrar is not detected on startup.
Can you run what @sanderjo said?

Could you switch logging to Debug (in the Status Window) and then after it happens again, post the part of the log before and after that error here.
Then we can start debugging.

Also: what version of SAB?

Hmm, ik denk dat het in de 2.0.0 versie komt. De volgende Beta

Je hebt helemaal gelijk. Het is een bug.
We hebben wat kapot gemaakt!

Ik ga het fixen maar moet even kijken wanneer dat in een uiteindelijke release komt.

Plaats de link maar! Ik zie misschien al waar het mis gaat..

Heb je toevallig niet een virusscanner die dat verwijderd?
Er is niks aangepast namelijk van 120 naar 121 wat betreft zip.
Heb je misschien exe in je cleanup-list staan? (Config Switches)

Is there anything in the log? You can search for the server-name.
After setting the Logging to +Debug.

Yes let us know if this helps!

If you could share failing and non-failing NZB's with us, that would be great.
Can be via PM or email.

If it still fails: could you also try SABnzbd 2.0.0Alpha1?

I am surprised. It seems more likely that it's a drop in network/newsserver than 2.0.0.
The improvements in 2.0.0 have been so great that it can only be similar, not slower.
Maybe keep watching it for a few more downloads?

It's the decoder failing for some reason.
Could you 2.0.0? It's still a testing release, but the decoder is very different so it might fix the issue.

Smpl is outdated, doesn't scale, uses ancient Javascript and all the extra code required for 2 interfaces made it very messy...
Two interfaces was from a time before Glitter could scale to different devices.