SABnzbd Forums

Hello,

I noticed some downloads in SABnzbd recently which are marked as failed. Hitting the retry button does not solve the problem, after a while the Download is marked again as failed.

I found out, that par2 is crashing:

There are 254 recoverable files and 0 other files.
The block size used was 262272000 bytes.
There are a total of 254 data blocks.
The total size of the data files is 66332863854 bytes.

Verifying source files:

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted

I compiled par2 from source but unfortunately the crash is the same.

I dont know what to do now. Same archive on another machine is being verified by par2 without problems.

Do You habe an idea where to start ? Or where it would be better to ask ?

Regards,
Chris

Which HW
Which OS
Which par2 version

... same questions for the other machine

Its an arm device (kirkwood) (dockstar, debian wheezy, kernel 3.2.23).

The other machine where it works is debian wheezy amd64, on a PC with 4GB of ram.

Oh, and its par2cmdline version 0.4 .

If you can reproduce it on the dockstar command line, it's a dockstar problem, and I would report it in dockstar forum. Oh: it can be a hardware problem: bad memory, or something like that.

Ok I got it after experimenting on a bigger machine. To be able to use par2 on this download the swap memory must be set to a minimum of 512MB. At least for machines with only 128MB of physical ram.

schmitt56 wrote:Ok I got it after experimenting on a bigger machine. To be able to use par2 on this download the swap memory must be set to a minimum of 512MB. At least for machines with only 128MB of physical ram.

You "got it"? The solution? Or the crash?

I got the solution.

schmitt56 wrote:I got the solution.

OK. Good. To understand you: you are able to let par2 crash from the commandline on the bigger machine? (Big as in: 1+ GB RAM?)