Message11273

Author jeff.allen
Recipients jamesmudd, jeff.allen, stefan.richthofer, zyasoft
Date 2017-03-25.11:21:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490440886.89.0.351577052175.issue2536@psf.upfronthosting.co.za>
In-reply-to
Content
Impressive analysis Stefan. Not much I can add.

I suppose the finally clauses fail to operate because they need to allocate objects? It's almost as if a rul of successful finally clauses was that they should have all their object allocation done ahead of time. If once you run out of memory, all contracts enforced by finally are unreliable, the condition should not be handled too locally but propagate out to where all affected objects are dereferenced. But how can anyone know where that is?

Only one thought: even after it is (mis-)handled, is there any chance of spotting that we were, for a time, out of memory?
History
Date User Action Args
2017-03-25 11:21:26jeff.allensetmessageid: <1490440886.89.0.351577052175.issue2536@psf.upfronthosting.co.za>
2017-03-25 11:21:26jeff.allensetrecipients: + jeff.allen, zyasoft, stefan.richthofer, jamesmudd
2017-03-25 11:21:26jeff.allenlinkissue2536 messages
2017-03-25 11:21:26jeff.allencreate