Bug #10920
closedReschedule verification tasks resulting to OOM
0%
Description
Core and Scheduler contribute considerably to reduce the overall time of verification job solution by speculatively shrinking a memory limit for verification tasks. AFAIK, they reschedule verification tasks with CPU timeouts (indeed, too much time may be necessary, say, for the garbage collector to hit within the reduced memory limit). It looks that this is not the case for out of memory cases. For instance, you can look here (this the internally available link, please, request for rights).
Updated by Evgeny Novikov about 3 years ago
- Priority changed from High to Urgent
This is very unpleasant issue since we loose good verification results quite often.
Updated by Evgeny Novikov about 3 years ago
BTW, there is the "java.lang.OutOfMemoryError" exception rather than exceeding the overall memory limit, that can explain, why rescheduling does not work.
Updated by Evgeny Novikov about 3 years ago
- Status changed from New to Resolved
Ilja fixed the issue in branch out-of-mem-problem that undergoes testing at the moment.
Updated by Evgeny Novikov about 3 years ago
- Status changed from Resolved to Closed
All tests passed and demonstrated that the issue has gone, so, I merged the branch to master in 6fb78ab26.