Kbase P8620: Progress sesion lingers in memory after closure although all windows are hidden
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
SYMPTOM(s):
Using ADM.
Progress session lingers in memory after application is closed.
Application's visual objects (windows) are hidden and destroyed correctly.
Application is closed via a developer-defined UI trigger.
Trigger does containg "RUN dispatch ('destroy')".
CAUSE:
After "RUN dispatch ('destroy')", all visual objects are destroyed, but the program flows stays in a WAIT-FOR inside src\adm\template\windowmn.i; because there are no user-interface elements visible, from that point on it's impossible to fire the event that the WAIT-FOR statement is waiting for, therefore the program flow will be stuck in the WAIT-FOR forever and the Progress session will seem to linger in memory or hang.
FIX:
Add "APPLY 'CLOSE' TO THIS-PROCEDURE" at the end of your UI trigger.