2017-10-16 15:02:37 -0600 | received badge | ● Popular Question (source) |
2017-09-21 07:09:11 -0600 | received badge | ● Notable Question (source) |
2016-07-20 07:11:10 -0600 | received badge | ● Popular Question (source) |
2014-07-28 13:47:10 -0600 | received badge | ● Supporter (source) |
2014-07-28 13:46:54 -0600 | commented answer | How to read directory with images by VideoCapture? For using this in command line arguments in Visual Studio, see http://stackoverflow.com/questions/7882295/how-to-include-the-percent-character-in-the-visual-studio-debugger-command-line |
2014-07-02 11:20:19 -0600 | commented answer | Turn on/off multithreading? Does anyone know if the OpenCV pre-built Windows libraries are compiled with TBB? |
2014-07-01 19:39:40 -0600 | commented question | Turn on/off multithreading? How about if I didn't compile OpenCV from source? |
2014-07-01 12:19:19 -0600 | asked a question | Turn on/off multithreading? I just noticed that GridAdaptedFeatureDetector::detectImpl (in modules/features2d/src/detectors.cpp) uses cv::parallel_for_ in its implementation. I'm assuming that means that it uses multithreading to speed up the feature detection process. My question is: is there a way I can force this to run in serial? The motivation to turn off multithreading is to do performance testing, to see how my code runs faster or slower, serially, based on different code changes. Is there a compile flag or function call I need to do? |
2013-05-28 19:21:48 -0600 | received badge | ● Editor (source) |
2013-05-28 19:21:01 -0600 | answered a question | Invalid pointer, double free or corruption I think I solved my problem. In the code below, I kept reassigning the Mat variable image while looping through sub-directories of images. When I declared image in the innermost for-loop, I stopped having problems. Can anyone explain why reassigning image multiple times would eventually cause memory problems? |
2013-05-25 02:02:26 -0600 | received badge | ● Student (source) |
2013-05-25 01:55:58 -0600 | commented question | Invalid pointer, double free or corruption forgot to mention that in some instances the error was "double free or corruption" |
2013-05-25 01:54:15 -0600 | asked a question | Invalid pointer, double free or corruption I'm reading in many images to do feature extraction and training for an SVM, and I keep getting seemingly random segmentation faults when the code reads in over X images and tries to release a Mat object from a function: test.cpp:109 is the last line of this code block (return finalMask): I've been trying to narrow down the problem, but I can't seem to figure it out. In some examples, it fails on consistently on the 423rd image read in. Other times when I changed the code, it failed consistently on the 547th image. Can anyone point me in the right direction to debug this problem? |