1401852 - Crash in nvwgf2umx.dll | stdext::_Hash<T>::insert (Windows 8, GPU crash)

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P3)

Description

[Asif Youssuff]

This bug was filed from the Socorro interface and is 
report bp-4e19444c-97ef-4697-8400-25c421170921.
=============================================================

163 crashes in the last week, several from 57.

Comment 1

[Jerry Shih[:jerry] (UTC+8) (inactive)]

Could we have a value in telemetry environment to show whether the content uses remote decoding or not?

Comment 2

[Tzuhao Kuo [:kaku]]

(In reply to Jerry Shih[:jerry] (UTC+8) from comment #1)
> Could we have a value in telemetry environment to show whether the content
> uses remote decoding or not?

It looks like telemetry environment collects global information, but "remoting decoding or not" bounds to each media element.
A page might play several medial elements at the same time, but they might use different decoders, remort or not.
So, telemetry environment is not the right place to show the information.

Comment 3

[Anthony Jones (:ajones, :kentuckyfriedtakahe, :k17e)]

(In reply to Jerry Shih[:jerry] (UTC+8) from comment #1)
> Could we have a value in telemetry environment to show whether the content
> uses remote decoding or not?

This is available in crash reports under "Process Type" where blank means non-e10s. About half of these crashes are in the GPU process with the other half being non-e10s.