| Title | Uncollected finalization messages lead to retention |
| Status | open |
| Priority | nice |
| Assigned user | Gareth Rees |
| Organization | Ravenbrook |
| Description | Christian Schafmeister's compiler was retaining a lot of memory [1]. This was due to the failure to collect finalization messages promptly. |
| Analysis | It seems likely that this would be a common mistake for MPS beginners to make. It would be nice if the MPS would help detect this [2]. We have the following channels of communication with the client: 1. Assertion (programming errors only) 2. Result codes (dynamic failures only) 3. Messages (won't work here) 4. I/O (will corrupt program output) 5. Events So it looks as though the best way to provide help in this case is to improve the interface to the event system. |
| How found | customer |
| Evidence | [1] <https://info.ravenbrook.com/mail/2014/08/17/04-26-56/0/>[2] < https://info.ravenbrook.com/mail/2014/08/18/15-05-42/0/> |
| Created by | Gareth Rees |
| Created on | 2014-09-27 21:37:20 |
| Last modified by | Gareth Rees |
| Last modified on | 2014-10-02 13:30:06 |
| History | 2014-09-27 GDR Created. |