Hallo, Thomas Grill hat gesagt: // Thomas Grill wrote:
Am 11.02.2007 um 21:50 schrieb Tim Blechmann:
Well, then how should Pd solve the logical pitfalls in your opinion?
mark the object as deletable, if the messaging is happening, wait for the object to return from the message function, then it can be safely deleted.
exactly, but the object should not process any further messages when the mark is set. I recently encountered the same situation, and by debugging i found that the crash happens while traversing the outlets to see if the message should be sent to other objects. It would be easy to check for such a mark there.
I'm wondering: There are other, less obvious cases of suicide that currently lead to a crash. I encountered this when trying to close the Gem-window by watching for the <Esc> key with [gemkeyname] connected to [0, destroy(--[gemwin]. This also crashes Pd and according to IOhannes for a similar reason. Inserting a [delay] in between this will fix it as well. However here not a single object is deleted. Which object should be "marked" here?
Ciao