Behavior of exit_type status

[AJ]

We have been searching for a solution / override to the default behavior of exit_type status when startup / restoration of the browser session after a power fail event.

As we understand it:

• Chromium (in our case Windows 10 x64 / chrome.exe) sets the status to "Crashed" at process startup
• When/if the process exits cleanly, the status is updated to "Normal"
• On the subsequent invocation, chrome will read the exit_type status and decide how to launch the browser session

Our application / platform is unattended / kiosk. If a power fail event occurs, the system will reboot and present the Google Search page (on top of our main application UI). This behavior is not ideal. Previously, we were working around this behavior using the --app switch, but with version 91.0.4472.77 the behavior has changed.

I've done some quick searching, and didn't find any specific request or a way to override this default behavior. Specifically, no matter the status of the exit_type always launch the process assuming "Normal". If an officially supported override exists, it would be great to be directed to a doc page explaining its usage.

As of right now we are using a hacky workaround to update this status within the Preferences file prior to invoking the process.

Thanks for the assistance.

[PhistucK]

What about using (creating) an extension to set things up on any browser restart?

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

[AJ]

We can look into the extension approach. We'd really prefer something built-in (e.g. a basic command line override switch / parameter) to control the behavior. Extensions / usage have dependencies, config, etc. to deal with.

Thanks.

[PhistucK]

I could not find anything here -

https://peter.sh/experiments/chromium-command-line-switches/

Did you try to set startup pages?

If that does not work, I think an extension is your only option.

☆PhistucK

[AJ]

Yes, we have started looking at startup pages. In this particular case (unexpected exit / shutdown) on the next startup with the standard behavior I believe we would be possibly launching an additional browser tab which is also not ideal as we'd be chewing up additional memory (we run on fairly constrained unattended/kiosk hardware) and possibly cause other issues with our application with multiple instances running.

[AJ]

Also, yes, thank you for the link, we have also reviewed and didn't see anything either.

[Joe Mason]

I think it's worth filing a bug at https://bugs.chromium.org/p/chromium/issues/entry with your use case and setting the type to "feature request". I think the best component to use is "UI>Browser>Sessions". (Or search bugs.chromium.org for similar feature requests and "star" them.)

[Andy Clugston]

Will do. Thank you.