-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: 1.6.2
-
Component/s: libmongoc
-
None
-
Environment:Windows 10 64 bit
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I am trying to use this driver in a multi-threading application. I am using client pool and make sure that using a cursor is always done in the same thread.
However, if the first use is always successful (each are begining by mongoc_init(); and treminated by mongoc_cleanup() following ones frequently crash, always when destroying something. It says something about heap corruption or writing past the heap limit.
I have been able to avoid this by providing my own memory functions and resetting the vtable.
Is there another way to avoid these problems?