Decoder failure: Out of memory

[MiG]

Update: Not sure what was going on, but I've not had this with new posts for about two weeks now.

The strange thing is, that the test NZBs that I kept around, still produce said error.
Could this possibly be issues at my usenet provider (eweka), or some sort of combination of local and server issues?

[sander]

The strange thing is, that the test NZBs that I kept around, still produce said error.

If you're on Windows: AFAIK there has not yet been a new SABnzbd / SAByenc release for Windows. So ... same SAB, same errors. You have to wait for the new release.

On Ubuntu Linux, a new Sabyenc was released/pushed, on thus on Ubuntu it won't happen anymore.

[safihre]

Will sabyenc auto-update on Ubuntu?

[sander]

Will sabyenc auto-update on Ubuntu?

Yes, if you have the PPA enabled and you do updates on your Ubuntu:

Code: Select all

$ sudo grep -irn sabyenc /var/log/dp*
/var/log/dpkg.log.1:1962:2019-06-23 21:44:17 upgrade python-sabyenc:amd64 3.3.5-1 3.3.6-0ubuntu1~jcfp1~19.04
/var/log/dpkg.log.1:1963:2019-06-23 21:44:17 status half-configured python-sabyenc:amd64 3.3.5-1
/var/log/dpkg.log.1:1964:2019-06-23 21:44:17 status unpacked python-sabyenc:amd64 3.3.5-1
/var/log/dpkg.log.1:1965:2019-06-23 21:44:17 status half-installed python-sabyenc:amd64 3.3.5-1
/var/log/dpkg.log.1:1966:2019-06-23 21:44:17 status unpacked python-sabyenc:amd64 3.3.6-0ubuntu1~jcfp1~19.04
/var/log/dpkg.log.1:1968:2019-06-23 21:44:17 configure python-sabyenc:amd64 3.3.6-0ubuntu1~jcfp1~19.04 <none>
/var/log/dpkg.log.1:1969:2019-06-23 21:44:17 status unpacked python-sabyenc:amd64 3.3.6-0ubuntu1~jcfp1~19.04
/var/log/dpkg.log.1:1970:2019-06-23 21:44:17 status half-configured python-sabyenc:amd64 3.3.6-0ubuntu1~jcfp1~19.04
/var/log/dpkg.log.1:1971:2019-06-23 21:44:17 status installed python-sabyenc:amd64 3.3.6-0ubuntu1~jcfp1~19.04

[MiG]

The strange thing is, that the test NZBs that I kept around, still produce said error.

If you're on Windows: AFAIK there has not yet been a new SABnzbd / SAByenc release for Windows. So ... same SAB, same errors. You have to wait for the new release.

On Ubuntu Linux, a new Sabyenc was released/pushed, on thus on Ubuntu it won't happen anymore.

Ah, so it was a bug with SAB then?
Thanks, I'll retry when the new version is released

[sander]

Ah, so it was a bug with SAB then?
Thanks, I'll retry when the new version is released

The NZB was wrong (with negative and thus illegal values for Segment Bytes, so negative message sizes ...), and SAB fell into that trap ...

Detail: the problem was in SAByenc, which is written in C. And you know what they say: C is like a chainsaw: fast, efficient, and very dangerous.

Anyway: SAByenc and thus SABnzbd is protected as of now. On Windows: wait for the new release.

[MiG]

The NZB was wrong (with wrong / negative values), and SAB fell into that trap ...

Just noticed an entire page of posts happened since the last time I checked (I tend to leave tabs open for a long time)... Thanks everyone for confirming it's definitely not just my hardware

[aundersh]

Just like me, there was a problem with the decoder!