Chromium Singleton profile lock file remains locked

[TommyGymer]

Description

Shutdown occasionally causes the cef chromium profile lock to not be deleted or invalidated, preventing next program start. Currently unclear on the cause of this, though I suspect it happens when not shutting down gracefully.

Manual fix

Deleting the singleton chromium profile in .config fixes the issue:

rm -rf ~/.config/cef_user_data/SingletonLock

Log

❯ ./linux-wallpaperengine 1845706469
[0903/090354.624735:WARNING:resource_util.cc(94)] Please customize CefSettings.root_cache_path for your application. Use of the default value may lead to unintended process singleton behavior.
[0903/090354.806525:ERROR:process_singleton_posix.cc(353)] The profile appears to be in use by another Chromium process (28253) on another computer (fedora). Chromium has locked the profile so that it doesn't get corrupted. If you are sure that no other processes are using this profile, you can unlock the profile and relaunch Chromium.
[0903/090354.806591:ERROR:message_box_dialog.cc(146)] Unable to show a dialog outside the UI thread message loop: Chromium - The profile appears to be in use by another Chromium process (28253) on another computer (fedora). Chromium has locked the profile so that it doesn't get corrupted. If you are sure that no other processes are using this profile, you can unlock the profile and relaunch Chromium.
[0903/090354.806656:ERROR:main_runner.cc(251)] ContentMainRun failed with exit code 21
CefInitialize: failed
terminate called after throwing an instance of 'std::runtime_error'
  what():  CefInitialize: failed
Error: nu::shell::coredump_error

  × program coredump error
   ╭─[entry #23:1:1]
 1 │ ./linux-wallpaperengine 1845706469
   · ───────────┬───────────
   ·            ╰── coredump detected. received signal: 6
   ╰────

Checking for process 28253 or chromium using ps gave no result, implying that the process information has remained in the lock file after previous session shutdown.