| Title | No recovery mode after assertion failure |
| Status | open |
| Priority | nice |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | Since 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. |
| Analysis | We 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 found | inspection |
| Evidence | There is currently no evidence that this is a problem. |
| Observed in | 1.110.0 |
| Created by | Richard Brooksby |
| Created on | 2013-05-25 16:12:34 |
| Last modified by | Gareth Rees |
| Last modified on | 2014-04-10 13:17:37 |
| History | 2013-05-25 RB Created after closing job001153, just in case. |