Web browser can't browse anything - "The rendering process has been closed for this tab" [signal 4 ILL_ILLOPN]
Bug #1613258 reported by
Timo Jyrinki
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
New
|
Undecided
|
Unassigned | ||
Oxide |
Fix Released
|
Critical
|
Chris Coulson | ||
1.16 |
Fix Released
|
Critical
|
Chris Coulson | ||
1.17 |
Fix Released
|
Critical
|
Chris Coulson | ||
glibc (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
oxide-qt (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This is happening with a no-change rebuild of webbrowser-app, with the most likely candidate for the problem trigger being the new glibc 2.24 in yakkety-proposed.
Changed in glibc (Ubuntu): | |
importance: | Undecided → Critical |
Changed in glibc (Ubuntu): | |
status: | New → Invalid |
Changed in oxide: | |
status: | Confirmed → Triaged |
milestone: | none → branch-1.18 |
assignee: | nobody → Chris Coulson (chrisccoulson) |
Changed in oxide: | |
status: | Triaged → In Progress |
summary: |
- signal 4 ILL_ILLOPN in webbrowser-app tests (glibc upgrade?) + Web browser can't browse anything - "The rendering process has been + closed for this tab" [signal 4 ILL_ILLOPN] |
tags: | added: unity8-desktop |
Changed in oxide-qt (Ubuntu): | |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in oxide: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The failure appears to be in oxide itself. Have you done a rebuild of oxide against the new glibc?