https://bugs.kde.org/show_bug.cgi?id=459047
--- Comment #2 from ronaldaj <vanelbur...@hetnet.nl> ---
Note: The memory leak in the minimal example can be removed by adding an extra
delete[] testarray; In my original problem the array comes from outside
from Python. (it is a numpy array coming in through a swig interface, ) The
life time of the python array is under control of Python garbage collection.
There I have the following valgrind outptu:
```
==115608== 320 bytes in 4 blocks are definitely lost in loss record 6,737 of
8,021
==115608== at 0x483C583: operator new[](unsigned long) (in
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==115608== by 0x152A9AE8: patchExtractor::divide2DDoubleArray(double*&,
double**&, int, int) (patchExtractor.cpp:468)
==115608== by 0x152AB073: patchExtractor::calcInternalHistograms(int, int,
double*, int, int*, int, double*) (patchExtractor.cpp:1296)
==115608== by 0x152A4C65: patchExtractor_cpp_calcInternalHistograms
(patchExtractor_wrap.cpp:3641)
==115608== by 0x152A4C65: _wrap_patchExtractor_cpp_calcInternalHistograms
(patchExtractor_wrap.cpp:4739)
==115608== by 0x5F69C9: PyCFunction_Call (in /usr/bin/python3.8)
==115608== by 0x5F74F5: _PyObject_MakeTpCall (in /usr/bin/python3.8)
==115608== by 0x571163: _PyEval_EvalFrameDefault (in /usr/bin/python3.8)
==115608== by 0x5F6CD5: _PyFunction_Vectorcall (in /usr/bin/python3.8)
==115608== by 0x56BBF9: _PyEval_EvalFrameDefault (in /usr/bin/python3.8)
==115608== by 0x50BB2D: ??? (in /usr/bin/python3.8)
==115608== by 0x56BACC: _PyEval_EvalFrameDefault (in /usr/bin/python3.8)
==115608== by 0x5F6CD5: _PyFunction_Vectorcall (in /usr/bin/python3.8)
```
--
You are receiving this mail because:
You are watching all bug changes.
