Ubuntu
chromium-browser package

The snap being updated in the background causes both old and new tabs to die to SIGTRAP

Bug #1914918 reported by Avamander
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned
snapd (Ubuntu)
In Progress
High
Ian Johnson

Bug Description

The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well.

This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap-related change rolled out to users with absolutely amateur-tier testing.

Ubuntu: 20.04.2
Snap: 2.48+20.04
Chromium: 88.0.4324.150

Tags: snap
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Denissen (timodenissen) wrote :

We have at least one Ubuntu installation that was updated from 18.04 to 20.04 with the automatic transition to chromium in snap on channel stable.

Every now and then chromium tabs crash with the SIGTRAP error. Possible workarounds are:

* Restarting chromium, or (if this doesn't work)
* Restart the complete laptop

Please give details on how to collect log or debug data and where/how to post them here (just uploading files, using an Ubuntu command?)

Revision history for this message
Avamander (avamander) wrote :

There are no good workarounds either, it observably causes anomalies in apps. Some PWAs lose their state after a restart and it's infuriating.

Canonical should dogfood their own known breaking changes.

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Can you try running `sudo snap set system experimental.robust-mount-namespace-updates=false` ?

Revision history for this message
Avamander (avamander) wrote :

Ran it, will report back how it affects behaviour, thanks.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Before trying that (or in addition to it), can you please share the output of this command:

    snap get core experimental.refresh-app-awareness

If it is "false", then I strongly suggest changing it to true per https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736, and this bug should be marked a duplicate of bug #1616650.

tags: added: snap
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in snapd (Ubuntu):
status: New → Confirmed
Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

I'm seeing similar problem. The only solution I found is to close and reopen browser.

snap 2.48.3+20.10
snapd 2.48.3+20.10
series 16
ubuntu 20.10
kernel 5.8.0-41-generic

dasm@dell:~/git/canonical$ sudo snap get system experimental.refresh-app-awareness
error: snap "core" has no "experimental" configuration option
dasm@dell:~/git/canonical$ sudo snap get core experimental.refresh-app-awareness
error: snap "core" has no "experimental" configuration option
dasm@dell:~/git/canonical$ sudo snap set system experimental.refresh-app-awareness=true
dasm@dell:~/git/canonical$ sudo snap get system
Key Value
experimental {...}
refresh {...}
seed {...}

I'll report back if I'm still seeing issues with this behavior.

Revision history for this message
Dariusz Smigiel (smigiel-dariusz) wrote :

I've seen no problems for last 5 days, while before, I had to restart browser every couple hours.

Samuele Pedroni (pedronis)
Changed in snapd (Ubuntu):
importance: Undecided → High
assignee: nobody → Samuele Pedroni (pedronis)
Revision history for this message
Avamander (avamander) wrote :

> I've seen no problems for last 5 days, while before, I had to restart browser every couple hours.

Similar experience here with refresh-app-awareness + no robust-mount-namespace-updates. One problem I did see was related to audio output breaking. Restart fixed it. Might just be a Chromium anomaly I wouldn't attribute to snap.

Revision history for this message
Samuele Pedroni (pedronis) wrote :

setting `sudo snap set system experimental.robust-mount-namespace-updates=false` fixes it

but just leaving /tmp/.X11-unix untouched doesn't

Ian Johnson (anonymouse67)
Changed in snapd (Ubuntu):
assignee: Samuele Pedroni (pedronis) → Ian Johnson (anonymouse67)
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.