Timeout in Apple's GLSL compiler
Reported by
chromium...@gmail.com,
Jun 27 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3473.0 Safari/537.36 Steps to reproduce the problem: 1. Load the test case What is the expected behavior? No crash What went wrong? Crash Crashed report ID: aa0e2e2abc827c8b How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 69.0.3473.0 Channel: canary OS Version: OS X 10.12.6 Flash Version:
,
Jun 29 2018
As mentioned above, the crash is from shader compile taking too long. Is this expected from the test case? Also mentioned in the title crbug.com/781443 : that bug is marked as possible duplicate of 781147, which is fixed. Is this a new case of issue 781443 ?
,
Jul 30
issue 781443 is a heap overflow, so this is not a duplicate. Tagging for GPU triage and +cc ccameron@ since we have a crash report.
,
Sep 10
kbr@, can you look at this? ccameron@ is unavailable.
,
Sep 10
SwiftShader doesn't appear any where in the crash stack. Kai, could you please try to triage this? Is it reproducible?
,
Sep 12
I'll look at this when I get a chance, but I think a watchdog timeout is pretty low priority right now.
,
Sep 12
This crash is issue 672485, but since that's closed and we might have a repro case here, I'm not going to mark duplicate.
,
Sep 12
Info from crash report: OS Name, version Mac OS X, 10.12.6 16G1408 OS Family 10.12 (Sierra) device id 0x8086 0x0166 3rd Gen Core processor Graphics Controller vendor id 0x8086 Intel Corporation driver 10.25.19
,
Sep 14
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, Jun 27 2018Components: Internals>GPU