webbrowser-app crashed with SIGSEGV in pushbuf_kref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webbrowser-app (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
On my system the web browser can surf web pages but in a few seconds it crashes the app and sometimes my hole system, making it unresponsive and I have to switch off power (maybe kernel panic?). This happens the same with snap and debian versions. The crash file generated in /var/crash is attached below.
And here is what it displays in the terminal when crashing (There are a few sentences in spanish):
user@machine:~$ webbrowser-app
could not open containers config file "/home/
Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
Input device added: "Logitech USB Optical Mouse" "/dev/input/event3" QFlags(0x2)
Input device added: "HDA Intel Line Out Side" "/dev/input/
Input device added: "HDA Intel Front Headphone" "/dev/input/
Input device added: "HDA Intel Front Mic" "/dev/input/event4" QFlags(0x20)
Input device added: "HDA Intel Rear Mic" "/dev/input/event5" QFlags(0x20)
Input device added: "HDA Intel Line" "/dev/input/event6" QFlags(0x20)
Input device added: "HDA Intel Line Out Front" "/dev/input/event7" QFlags(0x20)
Input device added: "HDA Intel Line Out Surround" "/dev/input/event8" QFlags(0x20)
Input device added: "HDA Intel Line Out CLFE" "/dev/input/event9" QFlags(0x20)
Input device added: "AT Translated Set 2 keyboard" "/dev/input/event2" QFlags(0x1|0x10)
shm_open() failed: Permiso denegado
qml: Loaded 5 UA override(s) from file://
TouchSelectionC
[PERFORMANCE]: Last frame took 55 ms to render.
[1010/141119:
QNetworkManager
QNetworkManager
"Object path cannot be empty"
Violación de segmento (`core' generado)
tags: | added: crash nouveau |
summary: |
- Web Browser crashes randomly and sometimes with the entire system + webbrowser-app crashed with SIGSEGV in pushbuf_kref() |
Changed in webbrowser-app (Ubuntu): | |
importance: | Undecided → Medium |
I’ve been able to partially retrace the attached crash in a xenial VM.
The top of the stacktrace looks like this:
#0 0x00007f34785ad06c in pushbuf_kref (push=push@ entry=0x5562e3e 8adc0, bo=0x0, flags=<optimized out>) at ../../nouveau/ pushbuf. c:167 8adc0, retry=<optimized out>) at ../../nouveau/ pushbuf. c:506 x86_64- linux-gnu/ dri/nouveau_ dri.so
#1 0x0007f34785ad709 in pushbuf_validate (push=0x5562e3e
#2 0x0007f34737a8926 in ?? ()
from /usr/lib/