search

animetosho / ParPar

High performance PAR2 create client for NodeJS
202 stars 21 forks source link

parpar fails at terminate called after throwing an instance of 'std::bad_alloc' #52

Open alfablac opened 1 year ago

alfablac commented 1 year ago

using ngPost with parpar default global readme installation with npm on node 18.17 calling parpar with -s5M -r12% -p12% --progress stdout i get this error

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

animetosho commented 1 year ago

Is that the full output? Try running the command manually if that's not what you're already doing.
Are you perhaps low on available RAM?

alfablac commented 1 year ago

Don't think so... might be an error on ngPost? Running the command manually I get the full 100% processing from parpar, on ngPost it fails, will keep trying to debug =/

animetosho commented 1 year ago

Does the error occur immediately, or does it take a while? If the latter, you can try obtaining the exact command from the running process.

Also, which version of ParPar is it using?

alfablac commented 1 year ago

I'm in the latest v0.4.2

Still can't pinpoint what the error actually is. I don't think it's parpar. Running ngPost with their verbose output I see I get 100% in parpar, and it fails right away before posting. Sounds like a limitation in the number of threads for actual posting in ngPost. I can't use two posting servers at the same time. Already reported that there, but ngPost is not that active nowadays.

animetosho commented 1 year ago

Are you able to tell if it's actually ParPar emitting the message?

If you're seeing 100% completion, it's either ParPar emitting it on exit, or ngPost emitting it.