Thank you for writing back.
I was not able to reproduce the described error with version 2014.2.715. Please, refer to the video from my attempts and to the attached sample project.
Also, I general you can use the procdump
tool to generate a dump of your application at application termination time. When dumped all the thread stacks and you should see the one causing the exact exception.
Run procdump from a command prompt like this: procdump -ma -t -w ConsoleApplication2.exe
Then run your app outside of debugger. Once it terminates you should see output from procdump indicating that the process has terminates and that it is writing a dump file.
If you continue experiencing issues, please modify my sample on a way to replicate the undesired behavior get back to us with it.
I hope this helps.
Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos
and start improving your app based on facts, not hunches.