From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107660] [regression] Firefox crashes on any WebGL usage with latest libdrm Date: Wed, 22 Aug 2018 16:36:10 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0452022726==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 554926E2F8 for ; Wed, 22 Aug 2018 16:36:11 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0452022726== Content-Type: multipart/alternative; boundary="15349557711.BBe5E2FCA.24175" Content-Transfer-Encoding: 7bit --15349557711.BBe5E2FCA.24175 Date: Wed, 22 Aug 2018 16:36:11 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107660 Bug ID: 107660 Summary: [regression] Firefox crashes on any WebGL usage with latest libdrm Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: regression Severity: normal Priority: medium Component: libdrm Assignee: dri-devel@lists.freedesktop.org Reporter: kai@dev.carbon-project.org CC: emil.l.velikov@gmail.com I recently noticed, that tabs in Firefox (Debian package 61.0.1-1 and 61.0.2 from mozilla.org) started crashing on WebGL usage. The easiest trigger is to just visit https://maps.gogle.com/ Since I was pointed towards bug 107384, comment #6 on IRC by Michel D=C3=A4= nzer and I see the loader errors as he described on IRC, I'm assuming this is relate= d. I can't be 100 % sure, because I'm unable to get a proper backtrace from Fire= fox (see below). It doesn't seem to be the same issue though, because using a libdrm built from Git (f31fd57c60) doesn't fix the crashes for me. I tried attaching GDB to the content process by launching firefox with: $ MOZ_DEBUG_CHILD_PROCESS=3D1 firefox -safe-mode and then running # gdb /usr/lib/firefox/firefox $PID where $PID is replaced by the actual PID of the tab process, which firefox prints on the console when started with MOZ_DEBUG_CHILD_PROCESS=3D1. The attaching seems to run fine, gdb is loading a bunch of debug information for all the libraries and Firefox itself. But when I continue from the (gdb) prompt, I immediately run into an endless stream of SIGSYS errors like > Thread 1 "Web Content" received signal SIGSYS, Bad system call. > 0x00007f884b08b397 in __access (file=3D0x7f88370b3360 "/usr/share/gtk-3.0= /settings.ini", type=3Dtype@entry=3D0) at ../sysdeps/unix/sysv/linux/access= .c:27 > 27 ../sysdeps/unix/sysv/linux/access.c: No such file or directory. Probably the sandbox that prevents this? Sadly I haven't found a way around that yet. (Any pointers welcome. Maybe it's possible to instrument libdrm/radeonsi/=E2=80=A6 in a way, that helpful information can be dumped = somewhere, when the tab crashes.) Without GDB the tab just crashes and offers to be closed or reloaded. In the terminal window where I started Firefox (with a clean profile and in safe m= ode) I get the following error: > libGL error: MESA-LOADER: failed to retrieve device information > libGL error: unable to load driver: amdgpu_dri.so > libGL error: driver pointer missing > libGL error: failed to load driver: amdgpu > libGL error: MESA-LOADER: failed to retrieve device information > libGL error: unable to load driver: amdgpu_dri.so > libGL error: driver pointer missing > libGL error: failed to load driver: amdgpu > [Parent 20860, Gecko_IOThread] WARNING: pipe error (47): Connection reset= by peer: file /build/firefox-tG9MzV/firefox-61.0.1/ipc/chromium/src/chrome= /common/ipc_channel_posix.cc, line 353 > [Parent 20860, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /bu= ild/firefox-tG9MzV/firefox-61.0.1/ipc/chromium/src/chrome/common/ipc_channe= l_posix.cc, line 709 >=20 > ###!!! [Parent][MessageChannel] Error: (msgtype=3D0x160068,name=3DPBrowse= r::Msg_SynthMouseMoveEvent) Channel error: cannot send/recv >=20 >=20 > ###!!! [Parent][MessageChannel] Error: (msgtype=3D0x16007F,name=3DPBrowse= r::Msg_Destroy) Channel error: cannot send/recv The graphics stack I used (fully updated Debian testing as a base) for test= ing is: GPU: Hawaii PRO [Radeon R9 290] (ChipID =3D 0x67b1) Mesa: Git:master/5fab32ddad libdrm: Git:master/f31fd57c60 LLVM: SVN:trunk/r340334 (8.0 devel) X.Org: 2:1.20.0-3 Linux: 4.18.3 Firmware (firmware-amd-graphics): 20180518-1 libclc: Git:master/62a9191b60 DDX (xserver-xorg-video-amdgpu): 18.0.1-1+b1 Let me know, if you need anything else. --=20 You are receiving this mail because: You are the assignee for the bug.= --15349557711.BBe5E2FCA.24175 Date: Wed, 22 Aug 2018 16:36:11 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 107660
Summary [regression] Firefox crashes on any WebGL usage with latest l= ibdrm
Product DRI
Version XOrg git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Keywords regression
Severity normal
Priority medium
Component libdrm
Assignee dri-devel@lists.freedesktop.org
Reporter kai@dev.carbon-project.org
CC emil.l.velikov@gmail.com

I recently noticed, that tabs in Firefox (Debian package 61.0.=
1-1 and 61.0.2
from mozilla.org) started crashing on WebGL usage. The easiest trigger is to
just visit https://maps.gogle.com/

Since I was pointed towards bug 107384, comment #6 on IRC b=
y Michel D=C3=A4nzer and
I see the loader errors as he described on IRC, I'm assuming this is relate=
d. I
can't be 100 % sure, because I'm unable to get a proper backtrace from Fire=
fox
(see below). It doesn't seem to be the same issue though, because using a
libdrm built from Git (f31fd57c60) doesn't fix the crashes for me.

I tried attaching GDB to the content process by launching firefox with:
 $ MOZ_DEBUG_CHILD_PROCESS=3D1 firefox -safe-mode
and then running
 # gdb /usr/lib/firefox/firefox $PID
where $PID is replaced by the actual PID of the tab process, which firefox
prints on the console when started with MOZ_DEBUG_CHILD_PROCESS=3D1. The
attaching seems to run fine, gdb is loading a bunch of debug information for
all the libraries and Firefox itself. But when I continue from the (gdb)
prompt, I immediately run into an endless stream of SIGSYS errors like
> Thread 1 "Web Content" received signal=
 SIGSYS, Bad system call.
> 0x00007f884b08b397 in __access (file=3D0x7f88370b3360 "/usr/share=
/gtk-3.0/settings.ini", type=3Dtype@entry=3D0) at ../sysdeps/unix/=
sysv/linux/access.c:27
> 27      ../sysdeps/unix/sysv/linux/access.c: No such file or directory=
.
Probably the sandbox that prevents this? Sadly I haven't found a way around
that yet. (Any pointers welcome. Maybe it's possible to instrument
libdrm/radeonsi/=E2=80=A6 in a way, that helpful information can be dumped =
somewhere,
when the tab crashes.)

Without GDB the tab just crashes and offers to be closed or reloaded. In the
terminal window where I started Firefox (with a clean profile and in safe m=
ode)
I get the following error:
> libGL error: MESA-LOADER: failed to retrieve dev=
ice information
> libGL error: unable to load driver: amdgpu_dri.so
> libGL error: driver pointer missing
> libGL error: failed to load driver: amdgpu
> libGL error: MESA-LOADER: failed to retrieve device information
> libGL error: unable to load driver: amdgpu_dri.so
> libGL error: driver pointer missing
> libGL error: failed to load driver: amdgpu
> [Parent 20860, Gecko_IOThread] WARNING: pipe error (47): Connection re=
set by peer: file /build/firefox-tG9MzV/firefox-61.0.1/ipc/chromium/src/chr=
ome/common/ipc_channel_posix.cc, line 353
> [Parent 20860, Gecko_IOThread] WARNING: pipe error: Broken pipe: file =
/build/firefox-tG9MzV/firefox-61.0.1/ipc/chromium/src/chrome/common/ipc_cha=
nnel_posix.cc, line 709
>=20
> ###!!! [Parent][MessageChannel] Error: (msgtype=3D0x160068,name=3DPBro=
wser::Msg_SynthMouseMoveEvent) Channel error: cannot send/recv
>=20
>=20
> ###!!! [Parent][MessageChannel] Error: (msgtype=3D0x16007F,name=3DPBro=
wser::Msg_Destroy) Channel error: cannot send/recv

The graphics stack I used (fully updated Debian testing as a base) for test=
ing
is:
GPU: Hawaii PRO [Radeon R9 290] (ChipID =3D 0x67b1)
Mesa: Git:master/5fab32ddad
libdrm: Git:master/f31fd57c60
LLVM: SVN:trunk/r340334 (8.0 devel)
X.Org: 2:1.20.0-3
Linux: 4.18.3
Firmware (firmware-amd-graphics): 20180518-1
libclc: Git:master/62a9191b60
DDX (xserver-xorg-video-amdgpu): 18.0.1-1+b1

Let me know, if you need anything else.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15349557711.BBe5E2FCA.24175-- --===============0452022726== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0452022726==--