09-19-2011 05:26 AM
I am using tbbmalloc_proxy on my project.
If I compile a templated SmartPointer class with standard allocator, everything is OK (and it is used like this since a while).
When I enable the tbb allocator replacements, it produces an unexpected "Access Violation writing location" while initializing the reference counter "count" value.
This constructor is called by an inlined templated class which handles reference counter creation, used by the templated smart pointer constructor.
My TBB version comes with 2011 tools.
Thanks for any advice.
09-19-2011 09:41 AM
My mistake, it was taking place in a complete test suite of over 50 classes, and it took me some time to conclude that TBB was not in cause. In fact, memory was messed up before the smart pointer tests, and the different memory management of TBB helped us to detect this issue !