Hello, after a glimpse into its sources I can see that there is InitializeCriticalSection() called in pthread_cond_init().
InitializeCriticalSection() is known to "leak" since Windows Vista: It allocates some kind of debug block which is then never released. If it is not desired behavior, InitializeCriticalSectionEx(CRITICAL_SECTION_NO_DEBUG_INFO) should be used instead. However InitializeCriticalSectionEx() is only available on Vista and newer as well, so for compatibility with Windows XP, it would have to use soma magic with GetProcAddress() to use one or the other. So if you are using pthread_cond_init() this could explain it. Martin Dne 30. 12. 2015 v 11:58 Vincent Torri napsal(a): > Hello > > With my little mem checker, i detect that winpthread does not free all > the resources it allocates. Is it normal ? > > thank you > > Vincent Torri > > ------------------------------------------------------------------------------ > _______________________________________________ > Mingw-w64-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
