Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Potential deadlock when autostarting webapps

Description

I added the "run-by-default" feature to the html5-launcher application (gerrit patch ). I expected the launcher to be run on startup, but it doesn't always happen. I suspect there is some kind of deadlock with the WAM initialization, and because of that, sometimes it works and sometimes (most of them) it doesn't.

Reproduced with RPi3.

Environment

None

Attachments

3

Activity

Walt Miner 
November 19, 2019 at 4:20 PM

Close for HH 8.0.3 release

Jacobo Aragunde Pérez 
October 16, 2019 at 9:10 AM

All related patches have been merged, for master and halibut branches.

jose bollo 
October 11, 2019 at 1:05 PM

I just submited it https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/22621

I was waiting to include or not an evolution linked to voice agents

Jacobo Aragunde Pérez 
October 11, 2019 at 12:38 PM
(edited)

Almost everything is done here, except bumping the version of app-framework-main in the recipe (edit: for halibut branch only). There are other commits involved, do you want me to send the revision bump patch?

Jacobo Aragunde Pérez 
October 7, 2019 at 12:03 PM

Answering 's question here too for future reference.

A unit dependency would require to create a solution similar to weston-ready, because the unit being up doesn't mean WAM is ready to listen to connections yet.

This solution was simpler to implement and doesn't require webapp units to depend on one specific service, and alternative browsers could be used (although that's probably not a concern at this point because we are providing WAM as an AGL module).

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Affects versions

Priority

Created September 3, 2019 at 11:48 AM
Updated November 19, 2019 at 4:20 PM
Resolved October 16, 2019 at 9:10 AM