Just-in-time (JIT) debugging instead of this dialog box. See the end of this message for details on invoking If you know what data the app is currently working with, and if you can purge that data, you may be able to get back to a clean and functional starting point. If the same crash still occurs, you might want to contact the app developer and to send them the same screenshot.ĮDIT: It's possible the data which is being worked on is itself somehow mangled, but strictly speaking the fact that the app cannot seem to deal with that gracefully is still a bug in the app. The key is to work out which app is crashing and then to update it to the latest available version. It's apparently some sort of front-end for a mySql database, if that helps to narrow it down. The app happens to rely on Visual Basic.Net, but that's not particularly important in this situation.
Otherwise, if you click 'Quit', the app will simply close and terminate at this point.' If you coded this application, or if you simply feel like delving into its code and you know what you're doing, feel free to have a go at just-in-time (JIT) debugging of this app. Since the app itself did not provide any means of recovering from this predicament, a crash is now inevitable. 'This application is about to crash because of an invalid attempt to convert a type of data to something which is incompatible.
