first chance overflow

[hazarada]

Yesterday i finished a project ive been working on for weeks or well i thought i had finished it.. in VS debug environment it runs fine doing its logics for hours without a problem but after publishing it as a standalone it starts throwing errors pretty soon. Took another look at whats going on in VS debug and the only thing that stands out is "A first chance exception of type 'System.OverflowException' occured.." that pops up every now and then so i think this is whats crashing my program outside vs. This poses 2 problems a) the code is around 2k lines/3 classes and heavily multithreaded and i have no clue where exactly this error gets generated, b) from my previous encounters with first chance exceptions they seem like more "possibility for error" instead of an actual error itself and very hard to track down

any tips on finding the problem? thanks.

[jmcilhinney]

A first chance exception means an exception has been thrown. A second chance exception means that a thrown exception hasn't been caught, so the app will crash or the debugger's Exception Assistant will be invoked.

The VB application framework provides an UnhandledException event you can handle to catch any unexpected exceptions. It's best to exit from that event handler unless you can confirm that the app is still in a valid state, but at least you are able to log the issue to help you work out where and why it occurred.