SQL*Forms run-time memory usage

From: Michael Greenberg <michael_at_mcil.comm.mot.com>
Date: 14 Jun 1994 19:04:10 GMT
Message-ID: <2tkuva$dao_at_delphinium.cig.mot.com>


We seem to be having memory leakage problems with SQL*Forms.

Users enter our SQL*Forms application in the morning and remain in it throughout the day. The application starts out running with less thank 500 K-bytes of memory in the data section. By the end of the day, the data section of the program can grow to over 20,000 K-bytes!

The application uses only NEW_FORM and does not use CALL_FORM.

In order to attempt to find out where the memory was being allocated, MESSAGE statements were added so that the application would pause at various places in order to get a snapshot of the memory requirements.

The application does not have MESSAGE calls in it. However, at one point where two MESSAGE commands were added for debug, one after the other as follows:

   MESSAGE('string 1');
   MESSAGE('string 2');

the program pauses and waits for an 'enter' after the first MESSAGE. After the 'enter' key is pressed the data area of the program increases by 4,096 bytes! Although this does not happen every time through this code, it happens often enough that it can be duplicated on demand. When the increase in data memory occurs, it is always after the first MESSAGE call.

Could the MESSAGE problem above be related to the fact that our SQL*Forms application run-time data area requirements increase from 500 K-bytes to 20 M-bytes (even though our application does not call MESSAGE)?

Could someone explain SQL*Forms run-time memory allocation?

Product versions:

   Oracle: 6.0.34.2.1
   SQL*Forms: 3.0.16
   PL/SQL: 1.0.34.0.1

   OS: HP-UX 8 and 9

Thanks in advance,
Michael
(michael_at_mcil.comm.mot.com) Received on Tue Jun 14 1994 - 21:04:10 CEST

Original text of this message