Consultor Eletrônico



Kbase P131572: 4GL/ABL: Application crashes executing code to populate a static WORK-TABLE.
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   5/16/2008
Status: Unverified

FACT(s) (Environment):

Progress 9.1B
Windows

SYMPTOM(s):

4GL/ABL: Application crashes executing code to populate a static WORK-TABLE.

Application crashes without giving any error message and the application window disappears from the windows desktop.

Application worked fine in the past.

CHANGE:

The database tables feeding the WORK-TABLE increased significantly in size.

CAUSE:

The WORK-TABLE is stored in memory. The code attempts to load enormous amounts of data into the WORK-TABLE consuming enough memory to cause a GPF in the 4GL session.

FIX:

Change the offending WORK-TABLE definition in the application to a TEMP-TABLE definition to avoid consuming too much of the system memory and causing a performance degradation or even a session crash.
Since the WORK-TABLE is stored in memory, loading large amounts of data into a WORK-TABLE, a proportionally large amounts of system memory will be needed to store that WORK-TABLE data.
Since the TEMP-TABLE is stored on the hard disk, no excessive use or appropriation of system memory resources is needed. All the session's TEMP-TABLEs are stored in the Temporary Client Session File DBI which is located in the session's current Working Directory or in the session's Temporary Directory as defined by the -T Client Session Startup Parameter.