Kbase P17514: Memory Leak when assigning data to a MEMPTR
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/01/2009 |
|
Status: Verified
SYMPTOM(s):
Assigning data to a MEMPTR causes a memory leak
Source of data (right hand side of the assignment) evaluates to a MEMPTR
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.0x
All Supported Operating Systems
CAUSE:
Bug# OE00086383
CAUSE:
When a MEMPTR is assigned the data in another MEMPTR (or the result from a function that returns one such as GET-BYTES() ), this target MEMPTR variable does not get its memory freed automatically before the assignment takes place. The reason for this is that there could be more than one pointer pointing at the same memory - MEMPTRs on which SET-POINTER-VALUE was used for example. Freeing the memory creates a considerable risk of memory violations in this case.
FIX:
Upgrade to OpenEdge 10.1A or later