Opened 20 years ago
Closed 20 years ago
#841 closed defect (fixed)
memory leaks from msInsertLayer
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | highest | Milestone: | 4.4 release |
Component: | MapServer C Library | Version: | 4.3 |
Severity: | normal | Keywords: | |
Cc: |
Description
Inserting a layer into a mapObj results in largish memory leaks ==5329== 1148 bytes in 7 blocks are definitely lost in loss record 73 of 88 ==5329== at 0x1B904A80: malloc (vg_replace_malloc.c:131) ==5329== by 0x1C004D5F: initHashTable (maphash.c:35) ==5329== by 0x1C011819: initClass (mapfile.c:1592) ==5329== by 0x1C056FA5: msCopyLayer (mapcopy.c:668) ==5329== by 0x1C067F22: msInsertLayer (mapobject.c:454) ==5329== by 0x1BFCDC4C: mapObj_insertLayer (mapscript_wrap.c:1313) ==5329== by 0x1BFECA81: _wrap_mapObj_insertLayer (mapscript_wrap.c:16433) ==5329== by 0x80EA40C: PyCFunction_Call (in /usr/bin/python) ==5329== by 0x805B3B6: PyObject_Call (in /usr/bin/python) ==5329== by 0x80AB92A: (within /usr/bin/python) ==5329== by 0x80A93C7: (within /usr/bin/python) ==5329== by 0x80A9B5D: PyEval_EvalCodeEx (in /usr/bin/python) ==5329== ... ==5329== ==5329== 3920 bytes in 7 blocks are definitely lost in loss record 80 of 88 ==5329== at 0x1B904A80: malloc (vg_replace_malloc.c:131) ==5329== by 0x1C01183E: initClass (mapfile.c:1597) ==5329== by 0x1C056FA5: msCopyLayer (mapcopy.c:668) ==5329== by 0x1C067F22: msInsertLayer (mapobject.c:454) ==5329== by 0x1BFCDC4C: mapObj_insertLayer (mapscript_wrap.c:1313) ==5329== by 0x1BFECA81: _wrap_mapObj_insertLayer (mapscript_wrap.c:16433) ==5329== by 0x80EA40C: PyCFunction_Call (in /usr/bin/python) ==5329== by 0x805B3B6: PyObject_Call (in /usr/bin/python) ==5329== by 0x80AB92A: (within /usr/bin/python) ==5329== by 0x80A93C7: (within /usr/bin/python) ==5329== by 0x80A9B5D: PyEval_EvalCodeEx (in /usr/bin/python) ==5329== by 0x80AB34B: (within /usr/bin/python)
Change History (3)
comment:1 by , 20 years ago
Milestone: | → 4.4 release |
---|---|
Priority: | high → highest |
Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.