tag:blogger.com,1999:blog-3285677929777490656.post4306377381542752698..comments2023-10-31T13:16:01.375+03:00Comments on Open CASCADE notes: Developing parallel applications with Open CASCADE. Part 2Roman Lyginhttp://www.blogger.com/profile/18338419158437898791noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3285677929777490656.post-91016743565133161232010-05-20T14:48:56.576+04:002010-05-20T14:48:56.576+04:00I've upgraded to v3 and in release mode the ap...I've upgraded to v3 and in release mode the application got a lot further before crashing. I'll investigate in debug mode to see if it's related to memory usage.Mike Applebyhttp://www.iconasolutions.comnoreply@blogger.comtag:blogger.com,1999:blog-3285677929777490656.post-37127811670972824962010-05-19T14:27:35.008+04:002010-05-19T14:27:35.008+04:00#include'ing tbbmalloc_proxy.h in a single cxx...#include'ing tbbmalloc_proxy.h in a single cxx file is enough. What it basically does is linking with tbbmalloc_proxy.dll which (when loaded during run-time) replaces the calls to new, malloc, delete. etc.<br /><br />Regarding _CrtIsValidHeapPointer, this is an interesting issue. The tbb allocator should be able to recognize if the memory was allocated by it or by other (e.g. system) allocator. In the latter case it does not try to free it obviously. Which tbb version have you tried ? We have recently released 3.0 which might help. Could you try it and/or send a small reproducer so that we can try this with our development team at Intel ?Roman Lyginhttps://www.blogger.com/profile/18338419158437898791noreply@blogger.comtag:blogger.com,1999:blog-3285677929777490656.post-20959613722228384142010-05-19T12:29:28.069+04:002010-05-19T12:29:28.069+04:00Anonymous found the documentation and just needs t...Anonymous found the documentation and just needs to use the #include once in the main application. I did this but then I get a crash in debug mode with CrtIsValidPointer.<br /><br />This is caused by the destructor of std::vector< void*>. The crash is within _CrtIsValidHeapPointer. This suggests that some memory was allocated with one type of allocator in a different module, and trying to free the memory in the main module.<br /><br />I know the above is abit vague, but do you have any pointers as to what is going wrong?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3285677929777490656.post-74561856085124063932010-05-19T05:58:58.757+04:002010-05-19T05:58:58.757+04:00When you mention about including "#include &q...When you mention about including "#include "tbb/tbbmalloc_proxy.h"" within the source file, can this be done in the application's stdafx.h or does this need to be included in every file?Anonymousnoreply@blogger.com