Out of memory errors should be non-critical

[mkroetzsch]

In cases where reasoning exhausts my memory, I get:

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

It would be good if VLog could recover from this, i.e., free resources and throw an exception that VLog4j can check for.

[CerielJacobs]

I attempted to fix this, throwing a MaterializationException in this case. Ceriel

…

On 23 Aug 2019, at 14:36, Markus Krötzsch ***@***.***> wrote: In cases where reasoning exhausts my memory, I get: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc It would be good if VLog could recover from this, i.e., free resources and throw an exception that VLog4j can check for. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.