Kbase P25922: QUIT statement in OCX event procedure causes random issues
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/06/2005 |
|
Status: Verified
SYMPTOM(s):
QUIT statement in OCX event procedure
QUIT statement in Ocx.Tick of PSTimer
QUIT statement in a Treeview 6.0 nodeclick event procedure
The instruction at 0x... referenced memory at 0x... The memory cannot be "read"
Progress session crashes
Progress session hangs
Issue occurs only on specific machines
CAUSE:
This is a known issue being investigated by Development.
The process is dying because it is still in an operating system callback when system call "exit" is called. For some reason this causes the operating system (actually, a run time library function) to GPF.
FIX:
Use the PROCESS EVENTS statement one or more times before the QUIT statement.
This solves the problem by allowing all pending callbacks to be processed before the QUIT is executed.