This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 79%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
I have another error running another program.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 12%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Presumably these are programs you're writing - so you need to find the causes and fix them.
Press the Retry button to debug the issues.
That’s so strange because I didn’t change anything and it work just fine a few hours ago ( no error at all when I ran it).
In the case of TravelingSalesman.exe the debug heap has detected that it has been corrupted. In the other case it appears that NeuralNetwork.exe has requested its own termination.
It is now up to the developer to debug these two applications to determine the cause of the heap corruption in TravelingSalesman.exe and the reason why NeuralNetwork.exe has decided to terminate itself.
The first image with the heap corruption, it turns out I tried to delete unknown location on the heap. I am still not sure why NeuralNetwork.exe decides to terminate itself.
Select the Debug configuration and start NeuralNetwork from Visual Studio. When the dialog appears, press Retry. See the Call Stack window and try determining the cause.
Okay, so I was debugging through the code and the moment it finishes looping through a double for loop inside a constructor it crashes and sent me to this screen. This is strange, because unlike the other issue that I'd solved a few hours ago, I had not made any changes to my code for this project. It appears that the same code works just fine on my friend's laptop so I am not sure if my code is the issue here.
It appears that the debugger is now at an instruction that is not inside your code but is probably a dll loaded by the system into your process. Many times coding errors manifest in crashes with errors that appear to emanate from system dlls because those are the modules that are identified when the abnormal termination of the process is reported.
Be specific about the crash. Was there an error code or other text associated with it? What does the call stack look like?