title: Visual Studio debug mode throws breakpoints for opencv HoughLines()
body: <p>I'm using Visual Studio 2012 and OpenCv 3.0. I'm using the <code>HoughLines</code> function for line extraction. If I run the code in <strong>Release</strong> mode, the VS does not throw any errors/exceptions. </p>
  
  <p>If I run the code in Debug mode, than for the mentioned function (<code>HoughLines</code>) triggers a breakpoint in VS. If I let it continue, than the following exception is thrown:</p>
  
  <blockquote>
    <p>Unhandled exception at 0x77AAE753 (ntdll.dll) in trackingLines.exe:
     0xC0000374: A heap has been corrupted (parameters: 0x77AE4270).</p>
  </blockquote>
  
  <p>The exception is thrown at line 
  <code>_Container_proxy *_Parent_proxy = _Parent-&gt;_Myproxy;</code> in <strong>xutility</strong> file in <code>VS/VC/include</code></p>
  
  <p>How should I setup the Debug exception list in order to be able to debug my code without this exception?</p>
  
  <p>What causes this exception? </p>
  
  <p>My code:</p>
  
  <blockquote>
  <pre><code>#include &lt;iostream&gt;
  #include &lt;stdio.h&gt;
  #include &lt;ctime&gt;
  
  #include "opencv2/imgcodecs.hpp"
  #include "opencv2/highgui/highgui.hpp"
  #include "opencv2/imgproc/imgproc.hpp"
  #include "opencv2/video/tracking.hpp"
  
  #include "opencv\cv.h"
  #include "opencv\highgui.h"
  
  #include &lt;string.h&gt;
  #include &lt;iostream&gt;
  #include &lt;fstream&gt;
  
  using namespace cv;
  using namespace std;
  
  int main( int _argc, char** _argv )
  {
  Mat src, src_bev;
  Mat src_gray, src_d;  
  IplImage * imageIn = cvLoadImage("img1.jpg"); 
  src = cvarrToMat(imageIn,true);   
  int  lowThreshold = 32, ratio = 1;
  Canny( src, src_gray, lowThreshold, lowThreshold*((double)ratio/10+2), 3 );
  vector&lt;Vec2f&gt; lines;  
  HoughLines(src_gray, lines, 1, CV_PI/180, 100, 0, 0 );    
  return 0;
  }
  </code></pre>
  </blockquote>
  
  <p>Please don't mind that first I'm reading in an <code>Iplimage</code> and than I convert it to <code>Mat</code>. There are no problems with reading the image or displaying. The only problem is whit the <code>HoughLines</code> function call.</p>