I am definitely able to confirm that memory consumption builds due to
invoking GetImageDepth() via a POSIX thread. The rate that it builds
is image sensitive since some images cause GetImageDepth() to perform
more OpenMP loops.
In /proc/PID/smaps I see multiple memory-mapped regions (including
"heap") building at once.
Running under valgrind reports no leaks.
I changed the sole memory allocation used in GetImageDepth() to use
the resource-limited memory allocator and it did not report any leaks.
My own testing is under Ubuntu 20.04 using GCC 10.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
