Kbase P177603: System.AccessViolationException on WAIT-FOR after applying ENTRY
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/11/2010 |
|
Status: Unverified
SYMPTOM(s):
System.AccessViolationException on WAIT-FOR after applying ENTRY
Client crashes intermittently with System.AccessViolationException
System.AccessViolationException: Attempt to read or write protected memory. This is often an indication that other memory is corrupt.
PROEVENTS .NET Timer_Tick Progress.Lang.Object Handle:2025 discarded Processing database/socket operation
FACT(s) (Environment):
Using the following log types: 4GLTrace:4,ProEvents.*:4,DynObjects.UI:4,oo4GL.Rcode:3
Windows
OpenEdge 10.2B02 32-bit Service Pack
CAUSE:
Bug# OE00202393
CAUSE:
The crash occurs when using APPLY "ENTRY" immediately before the WAIT-FOR in a legacy ABL Dialog, followed by satisfying the WAIT-FOR and returning focus to the .NET form which called it.
FIX:
To work around this problem, instead of using APPLY "ENTRY" followed by the WAIT-FOR, combine the two using the FOCUS option of the WAIT-FOR statement.
e.g.
Instead of:
APPLY "ENTRY" TO FILL-IN-1 IN FRAME {&FRAME-NAME}.
WAIT-FOR GO OF FRAME {&FRAME-NAME}.
Change the code to:
WAIT-FOR GO OF FRAME {&FRAME-NAME} FOCUS FILL-IN-1.