https://bugs.kde.org/show_bug.cgi?id=464769
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com
--- Comment #10 from caulier.gil...@gmail.com ---
The memory leaks in fingerprints algorithm was already reported, but never
reproduced in development platforms. In fact it's memory allocated and
des-allocated at end of the digiKam session. It's not lost definitively.
The reason is unknown. It's possible due to compiler version used or Windows
core libraries versions which do not match exactly (or buggous, thanks M$)
We pass the source code in plenty of static analyzers, more and less
performant, and we never found problems. Idem for the runtime memory check, but
this one introduce time latency in the program, so if memory leaks are due to
race conditions, we will never able to investigate the problem and fix...
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
