OSX Crash on Window.close

[Tim James <tjames1 at bigpond dot net dot au>]

I have just spent a long time trying to debug a problem  and now find it seems to be a problem only in OSX RB runtime and IDE but not in Classic under OSX. ( I have not tried it under a rebooted OS 9.2.2)

The bug occurs when one window is closed and the system should activate the next front window.

In a random manner the application will crash at this point in OSX but not in classic mode (solid as a rock -never crashes)

The randomness is extreme - although perhaps time between opening the window and closing has some relevance

When the window is hidden not closed - there is not a problem either in X or Classic


1. Am I breaking a RB standard in assuming that control should pass to the next front window on closing the frontmost. (In IDE that window's activate event does fire before the crash.)

2. I ensure that the self.close statement is at the end of the event handler (an editfield) that received the escape character from the user that triggers the window close. In various tests I have shown that the crash comes after the the execution of the windows.close event. Is this legal code behaviour?

3. Because the application runs faultlessly in classic mode but disastrously in OS X I have presumed the problem is not in my code - but is this correct. Are there rules relating to OSX not related to classic or OS 9

Configuration details

OSX 10.2 ,RB  4.5.1fc1 Mac OS X,G4 733Mhz, Valentina Plugin

Can anyone shed any light ??

Tim James