New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 598009 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
not on Chrome anymore
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

context_lost_tests flaky on Win7 Release (ATI & NVIDIA)

Project Member Reported by zmo@chromium.org, Mar 25 2016

Issue description

Crashes happen in various tests randomly

Backtrace:
	IsSandboxedProcess [0x6289307B+2826059]
	IsSandboxedProcess [0x628920CE+2822046]
	IsSandboxedProcess [0x62892EC6+2825622]
	ovly_debug_event [0x621E95F3+9100611]
	IsSandboxedProcess [0x62893903+2828243]
	GetHandleVerifier [0x6117A06B+341307]
	GetHandleVerifier [0x6117A3E6+342198]
	GetHandleVerifier [0x611522A7+178039]
	GetHandleVerifier [0x61128570+6720]
	GetHandleVerifier [0x61128043+5395]
	GetHandleVerifier [0x61152FAA+181370]
	GetHandleVerifier [0x611534D6+182694]
	GetHandleVerifier [0x61128291+5985]
	GetHandleVerifier [0x6112826D+5949]
	IsSandboxedProcess [0x62891A6E+2820414]
	ChromeMain [0x61104031+588561]
	ChromeMain [0x61103F06+588262]
	ChromeMain [0x61101313+577011]
	ChromeMain [0x6107458B+107]
	GetUploadedReportsImpl [0x011C6B4D+2877]
	GetUploadedReportsImpl [0x011C63BB+939]
	IsSandboxedProcess [0x0121F53B+188683]
	BaseThreadInitThunk [0x7689337A+18]
	RtlInitializeExceptionChain [0x77A692B2+99]
	RtlInitializeExceptionChain [0x77A69285+54]
 

Comment 2 by vmi...@chromium.org, Mar 26 2016

Cc: vmi...@chromium.org
Status: Available (was: Untriaged)
Summary: context_lost_tests flaky on Win7 Release (ATI & NVIDIA) (was: context_lost_tests flaky on Win7 Release (ATI))
This is happening somewhat regularly on different Win 7 Release bots.

More examples:

  https://build.chromium.org/p/chromium.gpu/builders/Win7%20Release%20%28NVIDIA%29
  https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28NVIDIA%29


I didn't have time to reproduce this today.  In the next pixel wrangling shift we should locally try building Windows Release and running the context_lost tests to repeatedly failure.

  content/test/gpu/run_gpu_test.py context_lost --story-filter=GPUProcessCrashesExactlyOnce --pageset-repeat=1000 --max-failures=0

Comment 3 by kbr@chromium.org, Mar 28 2016

Cc: zmo@chromium.org bajones@chromium.org
 Issue 598349  has been merged into this issue.

Comment 4 by kbr@chromium.org, Mar 28 2016

Owner: jbau...@chromium.org
Status: Assigned (was: Available)
John, as you're pixel wrangler this week may I assign this to you? Please build Chrome in Release mode with the GYP variable dcheck_always_on=1 and let's try to reproduce this on a local workstation.

Status: WontFix (was: Assigned)
I don't think we've seen  this recently.

Sign in to add a comment