Par2cmdline allocation failure.

[nf33]

See image.

[animetosho]

Could you try again using a smaller block size (increase the -b number)? Your screenshot suggests it's over 4GB, which seems to be problematic on a number of PAR2 clients.

I actually did some testing recently and found that keeping the block size under 1GB is probably best for compatibility (MultiPar hard-codes the maximum block size at 1GB).

[nf33]

I tried smaller block size, didn't work.

[animetosho]

I had a quick look at this, trying a similarly sized set of files and parameters, and got the same problem. I haven't bothered trying to identify what the problem is exactly, but it'll need to get fixed.

I did notice that it seems to work better if you explicitly specify a memory limit, so perhaps try adding -m1024 to the parameter list and trying again?
(if this works, it might be that the auto memory limit detection selects values too big on systems with lots of physical RAM available)

[fabiorzfreitas]

Any progress on this issue? I'm having the same problem (running par2 c -s768000 -r15 files.rar.par2 files.part*.rar over 400 rar files). -m1024 seems to be working (I'm running it right now), but it's so slow it's not viable.

[animetosho]

You can try increasing the memory limit number and see if it helps.

Having said that, par2cmdline isn't exactly a performance oriented PAR2 client. Increasing the memory limit mostly helps with I/O bound scenarios, and I suspect it has limited effect beyond a certain point (particularly if you're CPU bound).
Perhaps try a more performance oriented client like Multipar or ParPar if you want faster speeds.

(still would be good to have a fix)

[fabiorzfreitas]

I actually did switch to ParPar, which worked fine. Increasing the memory limit resulted in the same error.