I see some inconveniences in the solutions provided:
--incognito switch removes cache, what is pretty bad in most circumstances.
(Copy-pasting chrome help )
Google Chrome has hundreds of undocumented command-line flags that are added and removed at the whim of the developers.
--disable-session-crashed-bubble depends of which version of chrome are you using, the most actual version v39 doesn't have this setting allowed.
The solution I did was to alter the user profile and overwrite the crash status to a normal close status, It's a simple hack that works perfect.
This is the script I run in kiosk-mode in a chrome-only session under Ubuntu 12.04 and 14.04
sed -i 's/"exited_cleanly": false/"exited_cleanly": true/' ~/.config/google-chrome/Default/Preferences
sed -i 's/"exit_type": "Crashed"/"exit_type": "None"/' ~/.config/google-chrome/Default/Preferences
google-chrome --kiosk "http://some_url"
It simply finds and replace the string
- exit_type": "Crashed"
- "exited_cleanly": true
- "exit_type": "None"
So, no matter how chrome has closed. It will always think it has closed gracefully.
(Tested in many chrome versions)