MPS issue job003493

TitleNo recovery mode after assertion failure
Assigned userRichard Brooksby
DescriptionSince changelist 179654 the MPS has continued after an assertion in the hot variety. We've always coded the MPS with this in mind, but there's more we could do to allow an application to continue for as long as possible with corrupted memory, to allow a user to, say, save their work.
AnalysisWe should find out how bad things are after an assertion fires. How well does the MPS limp along as it stands? If not well, then perhaps we could flip into a recovery mode where we allocate using a separate allocator, switch off GC, etc. etc. to try to continue for a while.
How foundinspection
EvidenceThere is currently no evidence that this is a problem.
Observed in1.110.0
Created byRichard Brooksby
Created on2013-05-25 16:12:34
Last modified byGareth Rees
Last modified on2014-04-10 13:17:37
History2013-05-25 RB Created after closing job001153, just in case.