Closed Bug 1375058 Opened 7 years ago Closed 7 years ago

Crash in [@ @0x405b17 ]

Categories

(Core :: Graphics: WebRender, defect)

Product:
Core
Component:
Graphics: WebRender
Version:
56 Branch
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jan, Unassigned)

References

Details

(Keywords: crash, nightly-community, Whiteboard: [gfx-noted])

Crash Data

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170621100251

Steps to reproduce:

Scrolled down a large twitter page with those prefs:

browser.tabs.remote.force-enable;true
gfx.webrender.enabled;true
gfx.webrendest.enabled;true
layers.acceleration.force-enabled;true
layers.gpu-process.enabled;true
layers.gpu-process.force-enabled;true
layers.gpu-process.max_restarts;50
media.hardware-video-decoding.force-enabled;true




Actual results:

Meldungs-ID 	Sendedatum
bp-d05f4fc0-613e-4289-b9b4-8634e0170621	21.06.17	16:45

The contents of the Nightly Window seems very "strange" (random) for a second, then everything was back to normal.

about:support says Fehlerprotokoll
(#0) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
(#1) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
(#2) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
(#3) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
(#4) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
(#5) Error	Receive IPC close with reason=AbnormalShutdown
(#6) Error	Receive IPC close with reason=AbnormalShutdown
(#7) Error	Receive IPC close with reason=AbnormalShutdown
(#8) Error	Receive IPC close with reason=AbnormalShutdown
(#9) Error	Receive IPC close with reason=AbnormalShutdown
(#10) 	CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Crash Signature: [@ @0x405b17 ]
Keywords: crash, nightly-community
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
See Also: → 1372243
As Bug 1372850 Comment 2 said, we should also follow Bug 1372850 Comment 3 on Linux platform.
Those harmless gpu process crashes went away by setting layers.acceleration.force-enabled back to false (default), I think.
(In reply to Darkspirit from comment #2)
> Those harmless gpu process crashes went away by setting layers.acceleration.force-enabled back to false (default), I think.
No crashes because of that for 1 day now.

For the record: Disabling the gpu-process on my Debian Testing x64 (Radeon RX480) with Webrender + Webrendest enabled is not an option:
Normally I get some tab crashes or "permanent graphical random inside the window" with background crashes like bug 1352092 I could normally fix by pressing Ctrl+W.
I made a small test and disabled the gpu-process: My whole browser crashed on every webrender/webrendest bug.

Resetting layers.acceleration.force-enabled yesterday was a fine solution, I only had webrender tab crashes so far.
Reproduced STR of bug 1352092 comment 11.
layers.gpu-process.force-enabled;false
layers.gpu-process.enabled;false
Summary: gpu-process crash in [@ @0x405b17 ] → Crash in [@ @0x405b17 ]
Blocks: stage-wr-trains
Component: Graphics → Graphics: WebRender
Priority: -- → P3
Whiteboard: [gfx-noted]
Priority: P3 → --
Whiteboard: [gfx-noted] → [wr-mvp] [triage] [gfx-noted]
Priority: -- → P2
Whiteboard: [wr-mvp] [triage] [gfx-noted] → [wr-mvp] [gfx-noted]
I haven't seen this for a long time.
Status: UNCONFIRMED → RESOLVED
Has STR: --- → no
Closed: 7 years ago
Resolution: --- → WORKSFORME
Priority: P2 → --
Whiteboard: [wr-mvp] [gfx-noted] → [gfx-noted]
You need to log in before you can comment on or make changes to this bug.