Great documentation, and features like: caching, arbitrary number of
bands, user plug-ins, ...
I've been testing using valgrind on linux, and there are only "possibly"
memory leaks,
which are all suppressed by
{
<insert_a_suppression_name_here>
Memcheck:Leak
match-leak-kinds: possible
fun:malloc
...
fun:_dl_init
}
My question is this: Are these flagged because of how OIIO is managing
memory,
or it becuase of how the linux OS is managing memroy? Here is the
detail of the
first such "leak":
==9696== 41 bytes in 1 blocks are possibly lost in loss record 1 of 18
==9696== at 0x4A0645D: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==9696== by 0x5558579: OpenImageIO::v1_2::ustring::make_unique(char
const*) (in /usr/lib64/libOpenImageIO.so.1.2.3)
==9696== by 0x53550CB: ??? (in /usr/lib64/libOpenImageIO.so.1.2.3)
==9696== by 0x3C7AC0F2D9: call_init.part.0 (in /usr/lib64/ld-2.18.so)
==9696== by 0x3C7AC0F3C2: _dl_init (in /usr/lib64/ld-2.18.so)
==9696== by 0x3C7AC01229: ??? (in /usr/lib64/ld-2.18.so)
Thank you.
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
