2014-09-19 08:02:50 -0600 | received badge | ● Self-Learner (source) |
2014-09-18 07:45:07 -0600 | answered a question | SparseMat spawning an breakpoint on .release() Solution (for Visual Studio 2010): Following this link, I modified my project Properties/Configuration properties/C++/Code generation/Runtime Library from Multithread(/MT) to DLL Multithread(/MD) in Release, /MTd to /MDd in Debug. That /MT setup must date back from when I tried to get all the speed I could from |
2014-09-05 01:56:24 -0600 | received badge | ● Student (source) |
2014-09-04 17:12:35 -0600 | asked a question | SparseMat spawning an breakpoint on .release() Using OpenCV 2.4.6 (also with 2.4.9) under Win8.1, VS2010 Express, x86 debug or release, I observe the following : Code raises a breakpoint (in debug & release) during the call to delete, warning for a potential heap corruption : The call to Release is not necessary, I just found out this behavior when SparseMat left a function and got deallocated ... this example is simpler and fails too. The same lines used with Mat instead of SparseMat work perfectly. Where is the blunder ? Only other reference here and it doesn't help. |