Should collect relevant GDI information on the dump in case of system misbehavior.
Reported by
an...@yandex-team.ru,
Nov 2 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 Steps to reproduce the problem: Exhaust GDI resources somehow, e.g. open too many windows. What is the expected behavior? Browser crashes intentionally when faced with GDI problem. What went wrong? In case of crash it should collect relevant information on the dump and send it. Did this work before? N/A Chrome version: 56.0.2908.0 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0
,
Nov 5 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9625fddb94caf89f7f967326bb662aced7b2d884 commit 9625fddb94caf89f7f967326bb662aced7b2d884 Author: anpol <anpol@yandex-team.ru> Date: Sat Nov 05 09:56:20 2016 Collect total counters in case of GDI failure. If a system instability is caused by some non-browser process, it will be known from the total usage counters when crash dump is received. Thus we can distinguish a case when some non-browser process is misbehaving from other kinds of system resource exhaustion. BUG= 661461 R=thestig@chromium.org Review-Url: https://codereview.chromium.org/2467283002 Cr-Commit-Position: refs/heads/master@{#430161} [modify] https://crrev.com/9625fddb94caf89f7f967326bb662aced7b2d884/base/debug/gdi_debug_util_win.cc
,
Dec 7 2016
,
Dec 14 2016
This looks like out of scope for TE, hence adding the respective label for it to triage further. Thank You!
,
Feb 12 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Nov 2 2016