Because this would be a behavior change, it would have to be a new function.
If there is a new Quit LabView function, please add a "force quit" option. The current function puts up a "Save Changes?" dialog box when used in the development environment., and there is no way to work around it.
As part of our application build process we run multiple instances of LabView as services under FireDaemon (see https://forums.ni.com/t5/BreakPoint/Santa-Claus-wish-list/td-p/1870119). It all works great, until the very last step, which is quitting. Because we use libraries and classes, there are always non-user "changes" when the Application Builder runs. We never want to save these changes, but since LabView is running as a service without a user interface, there is no way to dismiss the "save changes" button. Instead the idle application just sits there using 1.4 GB of RAM. I have had to resort to ugly hacks (taskkill) to get LabView to actually quit.
After writing the above I rewrote this using "Teriminate" function in WinAPI. Attached. I use conditional disable to check for Windows platform, but all it does for other platforms is chain the errors above. Gosh, why can't I attach anything in this forum?
