MacOS – set some sort of “never send error report” on an app that has to be force quit frequently

The why is quite simple from a high level detail. The kernel is dumping a bunch of diagnostics since one of the hundreds of processes that run all the time had a hiccup and the system couldn't tell you anything more helpful.

It's easy to have a language where you can describe nonsense or illogical ideas. Computers are math based, so if you tell them to divide 5 things by 0 an error arrives. Unless the programmer has considered that this error could happen and writes code to handle those exact errors, the kernel is the last line of defense and it has told you it's giving up and dumping information an engineer might be able to use to debug the problem.

If I was that engineer, I would notice that spotlight's mdworker process might have been the last one in the vicinity where the crash was logged and that the last change to the kernel was unloading MSDOS extension, so I would ask you if you have any PC drives connected or ejecting and if this crash was actually within 8 minutes (505 seconds) from the time the Mac was started.

Another high level analogy is if your car stalls, try starting it up again. Only if it's stalling in a repeated way or you have other needs (like you're driving the president around) would you try to fix it yourself or hire a team of engineers to know what to do. In your case, we would need to know a lot about what you have connected to the Mac, if you can boot from a clean install of the OS, if you have expertise or time to troubleshoot this or if you just want assurance on what to do next.

From a user level perspective, here are tips you can take to know how to handle them:

• OS X: About kernel panics - http://support.apple.com/kb/TS3742

Feel free to ask a follow on question if you have more context to this one panic dump or have questions how to use the article above to solve your dilemma.

We also have a few threads that might help you narrow down some options:

• OS X Mountain Lion - Kernel Panic and Restart after Sleep
• How to debug and solve an OS X 10.8 kernel panic which appears quite often, sometimes twice a day?
• computer sleeps, then crashes later

You should be able to use AppleScript:

tell application "name" to quit

Using 'to quit' rather than 'to force quit' will mean that it won't be forced regardless of whether the app is unresponsive—rather, it will ask the app to quit whenever it can.

With shell:

osascript -e 'tell application "name" to quit'