Kbase P12037: Memory Leak with 4GL Sockets
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
SCO OpenServer
FACT(s) (Environment):
Progress 9.1C
SYMPTOM(s):
Memory leak when using 4GL sockets
Memory leak occurs on secondary clients connecting to the database
CAUSE:
The 4GL programs did not properly manage memory pointers. A single memory was used for both reading and writing of data. When using sockets that should not be done as the asynchronous nature of sockets will cause the program to eventually be both reading from and writing to the socket at the same time.
FIX:
Use separate memory pointer variables. One for reading and a second one for writing.