Return code when MinisatID goes out of memory

Issue #465 resolved
JoD created an issue

IDP returns error code 0 instead of error code 134 when MinisatID aborts because of an OutOfMemoryException, generated by a memorylimit on IDP.

Attached is an output of an IDP run and the corresponding instance and specification which trigger this behaviour. ulimit was used to limit time to 1000s and memory to 4000 MB.

This issue is annoying when using Benchie, since some out of memory runs will not be identified as such.

Comments (3)

  1. Log in to comment