MPS issue job003864

TitleUncollected finalization messages lead to retention
Assigned userGareth Rees
DescriptionChristian Schafmeister's compiler was retaining a lot of memory [1]. This was due to the failure to collect finalization messages promptly.
AnalysisIt 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 foundcustomer
Evidence[1] <>
[2] <>
Created byGareth Rees
Created on2014-09-27 21:37:20
Last modified byGareth Rees
Last modified on2014-10-02 13:30:06
History2014-09-27 GDR Created.