I am calling a dialog box using a context menu from a table (purchase orders). When closing the dialog box using end_dialog(@window,Desc) subroutine OI crashes.

This only occurs in version 9.0. I performed an app backup and restored on OI verion 8.07 with no crashing. I use a similar technique in the sales orders with no problem (version 9.0). I have isolated the problem to the end_dialog subroutine. I think it is a version 9.0 issue. Do I need to go back to version 8.07 until version 9.01 is available.

Please advise

TIA

Chris

Chris-

A quick scan of the source code shows we haven't done anything to the Basic+ for End_Dialog and its related programs in years (about 15).

Has anything else changed? I'd like to track this down before the 9.0.1 release.

Thanks-

Mike

I spoke with David Goddard and he suggested I post this on the discussion. How can I help to solve the problem? What info do you need. Maybe you can log into my and see the problem.

Chris

Chris

Does this crash result in a "freed common" error message in the debugger ???

Where do I find the freed common in the debugger?

Chris

Does the debugger show when you have this crash? If it does then does it show a massage that says (approx) "labeled common variable has been freed"? This is an issue that I have had problems with for years although have made some progress lately . (see

http://www.revelation.com/__85256DC1002A4A9E.nsf/0/B376D696F66889688525738E00012B0B?OpenDocument

Chris can you e-mail us ([email protected]) the code on the close and in the program which calls the dialog box, or create a simple example that reproduces the problem and rdk that? I had another developer complain about the same issue but have not reproduced it. I suspect that this is indeed the same issue that Kevin has, that it is timing related, that there is an embedded assumption that the presentation server is not independent of the engine, and that when we sped things up or decoupled the presentation server we violated that assumption.

Also, I recently worked with a developer whose write event called sends the close message to the window. He found that when the user clicks on the X they get a savewarn message, if they save changes the write event fires, which fired his close. When control returned to the original close event it crashed OI. The solution was to use retstack to see if the window was already closing. His write event now has code like

declare function retstack

*

* … some processing

*

call forward_Event()

if index(Retstack(), 'CLOSE.WINDOW', 1) else

 Call Send_Event(@window, 'CLOSE')

end

Hi Bob / Chris

I had a situation recently that enabled me to create this issue sometimes (say once in 10 or 20 tests). I have spent several weeks working through a process of elimination as it is still just as important to me to fix this. Although I still do not understand what the mechanism of the issue is, I did find that if the "BITMAP" set property was not used the occurrence of issue in this test reduced (or maybe disappeared ??). I use the "BITMAP" property in the WINMSG event to change the images that the cursor flies over. I do not see how BITMAP relates to the closing of a dialog box however the experiment suggests a connection?. I have found that if I replace the BITMAP property with my own OSRead and an IMAGE property the same function is acheived with out the issue being apparent. Bob - as I say I dont really see the connection and this may be a false lead but it may help in same way…

Cheers Kevin

Thanks Kevin.

I believe that events are queing while the window is closing, arriving at the engine after it completes the close of the window.

Your remark is a clue to how messages are arriving out of sync.

Bob

Is there any way that I can 'see' the event queue and reorder before the close or some other fix in the mean time.

Thanks Kevin

View this thread on the Works forum...