Closed Bug 1144529 Opened 10 years ago Closed 8 years ago

SEGFAULT on some pages when layers.acceleration.force enabled

Categories

(Core :: Graphics, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: kami911, Unassigned)

Details

(Whiteboard: [gfx-noted])

Saving Eventbrite page and downloading attachments from gmail causes SEGFAULT wit this error on the console: [Child 32283] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/ipc/glue/MessageChannel.cpp, line 1589 [Child 32283] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/ipc/glue/MessageChannel.cpp, line 1589 [NPAPI 32384] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/ipc/glue/MessageChannel.cpp, line 1589 [NPAPI 32384] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/ipc/glue/MessageChannel.cpp, line 1589 I wasn't able to reproduce it with empty profile. Linux Mint 17.1 (Thrusty based), 64 bit, Ubuntu Nightly PPA, using E10s --host=x86_64-linux-gnu --prefix=/usr --libexecdir=/usr/lib/firefox-trunk '--with-l10n-base=/build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/./l10n' '--srcdir=/build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/.' --enable-release --disable-install-strip --disable-updater --enable-application=browser --enable-startup-notification --with-distribution-id=com.ubuntu --enable-optimize --enable-tests --disable-crashreporter --with-branding=browser/branding/nightly --disable-gnomevfs --enable-gio --enable-update-channel=nightly --disable-debug --disable-elf-hack --with-app-name=firefox-trunk --with-app-profile=.mozilla/firefox-trunk --enable-profiling --enable-gstreamer=1.0 '--with-google-api-keyfile=/build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/debian/ga' '--with-google-oauth-api-keyfile=/build/buildd/firefox-trunk-39.0~a1~hg20150312r233214/debian/go'
I have disabled all extension in the original profile but it still chrashes with SEGFAULT.
It seems layers.acceleration.force-enabled;true can cause this problem for me. Adapter Description X.Org -- Gallium 0.4 on AMD CAICOS Device ID Gallium 0.4 on AMD CAICOS Driver Version 3.0 Mesa 10.1.3 GPU Accelerated Windows 1/1 OpenGL (OMTC) Vendor ID X.Org WebGL Renderer X.Org -- Gallium 0.4 on AMD CAICOS windowLayerManagerRemote true AzureCanvasBackend cairo AzureContentBackend cairo AzureFallbackCanvasBackend none AzureSkiaAccelerated 0 lspci 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] lshv -C video *-display description: VGA compatible controller product: Seymour [Radeon HD 6400M/7400M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@0000:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:46 memory:c0000000-cfffffff memory:d4300000-d431ffff ioport:4000(size=256) memory:d4340000-d435ffff xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 libdrm-radeon1:amd64 2.4.56-1~ubuntu2 Linux Godzilla 3.16.0-31-generic #43~14.04.1-Ubuntu SMP Tue Mar 10 20:13:38 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Summary: SEGFAULT on some pages → SEGFAULT on some pages when layers.acceleration.force enabled
Any crash report links from about:crashes?
Component: DOM: Content Processes → Graphics
needinfo Kami for comment 3.
Flags: needinfo?(kami911)
Whiteboard: [gfx-noted]
I cannot find any crashinfo. No about:crashes. Maybe is this an unique property of Ubuntu PPA builds? I see --disable-crashreporter in the buildconfig :/
Flags: needinfo?(kami911)
(In reply to Kami from comment #5) > I cannot find any crashinfo. No about:crashes. Maybe is this an unique > property of Ubuntu PPA builds? > I see --disable-crashreporter in the buildconfig :/ Hmm, I guess the Ubuntu packagers disable crash reporting. If you're willing to try an upstream nightly build from https://nightly.mozilla.org/ instead, and then submit links to crash reports, that would help.
(In reply to Kami from comment #7) > https://crash-stats.mozilla.com/report/index/9f758b7f-a9b9-45db-907a- > 432de2150320 Thanks! The stack trace doesn't make much sense to me - the crash seems to be in GL driver code, but there are functions like nsRegion::Or() on the stack, which don't call into GL code... cc'ing Jeff in case he has any ideas.
It looks like we're crashing in the driver. Please file an upstream driver bug at bugs.freedesktop.org
Related Freedektop Bugzilla entry: https://bugs.freedesktop.org/show_bug.cgi?id=89745
Upstream bug was fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.