WAM is usually ran as a system service, which runs a shared browser process for all webapps, but there is an alternate mode. In case the shared browser process is not running (which is guessed by checking the existence of the lock file), the WAM launcher process should be able to boot a single browser process for use in that web application.
In Halibut, I checked that this mode is not working due to a crash. Steps to reproduce:
1. stop the wam service: systemctl stop WebAppMgr@1001.service
2. remove the lock file: rm /tmp/wamsocket.lock (affected by
3. start a webapp
We haven't tested this mode for a while, but I suspect it started crashing in Halibut due to the changes in permissions and users.