Issue metadata
Sign in to add a comment
|
Browser crash on Win 10 High-DPI Perf |
||||||||||||||||||||
Issue descriptionSeveral tests fail due to the clock sync error. The failure has been there for a few weeks. Affected bots are: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%281%29?numbuilds=200 https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%282%29?numbuilds=200 https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%284%29?numbuilds=200 Randy, can you take a look? Sample error: Traceback (most recent call last): _RunStoryAndProcessErrorIfNeeded at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\internal\story_runner.py:110 test.DidRunPage(state.platform) traced_function at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py:75 return func(*args, **kwargs) DidRunPage at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\tools\perf\measurements\smoothness.py:65 self._tbm.DidRunStory(platform) DidRunStory at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\web_perf\timeline_based_measurement.py:309 platform.tracing_controller.StopTracing() StopTracing at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\core\tracing_controller.py:47 return self._tracing_controller_backend.StopTracing() StopTracing at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py:108 self._IssueClockSyncMarker() _IssueClockSyncMarker at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py:203 self._RecordIssuerClockSyncMarker) RecordClockSyncMarker at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py:193 sync_id, record_controller_clock_sync_marker_callback) _RecordClockSyncMarkerAsyncEvent at C:\b\c\b\Win_10_High_DPI_Perf__4_\src\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py:170 'Failed to issue clock sync to devtools client') ChromeClockSyncError: Failed to issue clock sync to devtools client
,
Oct 3 2016
That error means that telemetry is no longer able to talk to chrome via devtools (usually meaning chrome crashed). On https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%281%29/builds/307/steps/jitter/logs/stdio https://uberchromegw.corp.google.com/i/chromium.perf/builders/Win%2010%20High-DPI%20Perf%20%281%29/builds/307/steps/thread_times.tough_scrolling_cases/logs/stdio and probably the rest of them You see this error before the clocksync errors: DevtoolsTargetCrashException: Devtools target crashed It does not appear to be related to issue 649333
,
Oct 3 2016
Ah I see. Ned, do you know how to triage browser crash type of failure. For this situation, we do not have access to the first failure.
,
Oct 3 2016
Hi Zhen, the way to triage these bug is to look at browser's stack: (C:\b\c\b\Win_10_High_DPI_Perf__1_\src\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py:416 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:64024/devtools/page/b396f4ef-8a79-43d3-8a3b-6dc4684067c7 Found Minidump: True Stack Trace: ******************************************************************************** Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\users\chrome~1.lab\appdata\local\temp\tmpn0tj9i\reports\8d58e1a0-f615-41e5-9c42-df0a7b9de895.dmp] User Mini Dump File: Only registers, stack and portions of memory are available ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\b\c\b\Win_10_High_DPI_Perf__1_\src\out\Release_x64 Symbol search path is: C:\b\c\b\Win_10_High_DPI_Perf__1_\src\out\Release_x64 Executable search path is: Windows 10 Version 10240 (16384) MP (4 procs) Free x64 Product: WinNt Built by: Windows NT 10.0.10240.16384 Machine Name: Debug session time: Mon Oct 3 11:04:19.000 2016 (UTC - 7:00) System Uptime: 0 days 1:51:51.909 Process Uptime: 0 days 0:00:01.000 ................................................................ ................................ Loading unloaded module list ......... This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (1240.238): Access violation - code c0000005 (first/second chance not available) *** WARNING: Unable to verify checksum for ntdll.dll *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - *** WARNING: Unable to verify checksum for KERNELBASE.dll *** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNELBASE.dll - ntdll!ZwDelayExecution+0xa: 00007fff`2180383a c3 ret 0:000> cdb: Reading initial command '.ecxr;kb30;~*kb30;q' *** WARNING: Unable to verify checksum for chrome.dll No .natvis files found at C:\b\c\b\Win_10_High_DPI_Perf__1_\src\out\Release_x64\cdb\Visualizers. rax=0000000000000000 rbx=000000866695d5b8 rcx=000000000000025e rdx=0000000000000000 rsi=0000000000000000 rdi=0000008666905fa0 rip=00007fff0351fec2 rsp=000000865d7dd4d0 rbp=000000865d7dd5d0 r8=0000000000000300 r9=00000000000004f4 r10=0000000000000000 r11=000000865d7dd360 r12=7fffffffffffffff r13=8000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei pl zr na po nc cs=0033 ss=0000 ds=0000 es=0000 fs=0053 gs=002b efl=00010246 chrome_7fff02490000!content::SyntheticGestureTargetBase::DispatchInputEventToPlatform+0x122: 00007fff`0351fec2 88042500000000 mov byte ptr [<Unloaded_Unknown_Module_00000000`00000000> (00000000`00000000)],al ds:00000000`00000000=?? RetAddr : Args to Child : Call Site 00007fff`03521037 : 00000001`90110023 00000086`6300d9a0 00000001`90110023 00007fff`035204a9 : chrome_7fff02490000!content::SyntheticGestureTargetBase::DispatchInputEventToPlatform+0x122 00007fff`03520ae9 : 00000001`90110023 00000000`00000000 00000000`00000000 00000000`00000000 : chrome_7fff02490000!content::SyntheticSmoothMoveGesture::ForwardTouchInputEvents+0x16b 00007fff`03521322 : 00000000`00000000 00000086`62ff50b0 00000086`5d7dd990 00000086`5d7dd9b8 : chrome_7fff02490000!content::SyntheticSmoothMoveGesture::ForwardInputEvents+0xad 00007fff`0351f360 : 00000086`667809a0 00000086`5d7dda40 00000086`00000000 00000086`5d7dd990 : chrome_7fff02490000!content::SyntheticSmoothScrollGesture::ForwardInputEvents+0x42 00007fff`03569d9b : 00000001`00000000 00000001`90110023 00000086`667809a0 00000086`6664a090 : chrome_7fff02490000!content::SyntheticGestureController::Flush+0xc8 00007fff`035750d6 : 00000001`90110023 00000086`5d7def01 00000000`00000000 00000086`627840e8 : chrome_7fff02490000!content::RenderWidgetHostImpl::FlushInput+0x37 00007fff`02f86796 : 00000086`00000000 00000086`6664a0d0 00000086`627a2950 00000086`5d7deff8 : chrome_7fff02490000!content::RenderWidgetHostViewAura::OnBeginFrame+0x2a 00007fff`025b4425 : 00000086`6664a090 00000086`66672460 00000000`00000001 00000086`5d7deff8 : chrome_7fff02490000!cc::DelayBasedBeginFrameSource::OnTimerTick+0x256 00007fff`025b4425 : 00000003`00000000 00000086`5d9b82f8 00000086`5d7deff8 0000bcdd`3c59eb57 : chrome_7fff02490000!base::internal::Invoker<base::internal::BindState<void (__cdecl base::CancelableCallback<void __cdecl(void)>::*)(void)const __ptr64,base::WeakPtr<base::CancelableCallback<void __cdecl(void)> > >,void __cdecl(void)>::Run+0x35 00007fff`02d066c3 : 00000086`00000000 00000000`00666ab3 00000000`00000000 00007fff`0554a358 : chrome_7fff02490000!base::internal::Invoker<base::internal::BindState<void (__cdecl base::CancelableCallback<void __cdecl(void)>::*)(void)const __ptr64,base::WeakPtr<base::CancelableCallback<void __cdecl(void)> > >,void __cdecl(void)>::Run+0x35 00007fff`02c99cd5 : 00000000`00000000 f400001c`0000001d 00000086`00666ac0 00007fff`00666ac0 : chrome_7fff02490000!base::debug::TaskAnnotator::RunTask+0x1a3 00007fff`02c99fd1 : 00000086`00000606 00000086`5d7deff8 00000001`90110015 00007fff`20adba10 : chrome_7fff02490000!base::MessageLoop::RunTask+0x455 00007fff`02c9ab44 : 00000003`5987f8c5 00000101`00000001 00000000`00000000 00000086`5d7df498 : chrome_7fff02490000!base::MessageLoop::DeferOrRunPendingTask+0x51 00007fff`02d06fbb : 00000086`5d9a8401 00000086`5d9a8440 00000086`5d7df501 00000086`000003c8 : chrome_7fff02490000!base::MessageLoop::DoDelayedWork+0x194 00007fff`02d06c64 : 00000086`5d7df540 00000086`5d9a8440 00000086`5d7df1a0 00007fff`02c9c5da : chrome_7fff02490000!base::MessagePumpForUI::DoRunLoop+0x8b 00007fff`02ce09bd : 00000086`5d7df1e0 00000086`5d7df540 00000086`5d7df1e0 00000086`5d7df498 : chrome_7fff02490000!base::MessagePumpWin::Run+0x54 00007fff`038a883c : 00000086`0066640b 00000086`5d9617e0 00000086`5d9617e0 00000086`5d7df480 : chrome_7fff02490000!base::RunLoop::Run+0xdd 00007fff`03372a82 : 00000000`00000000 00000086`5d961620 00007fff`00000000 00000086`5d7df480 : chrome_7fff02490000!ChromeBrowserMainParts::MainMessageLoopRun+0xbc 00007fff`033740d3 : 00007fff`04ff1c58 00007fff`04ff1c58 00000086`5d7df480 00000086`5d7df540 : chrome_7fff02490000!content::BrowserMainLoop::RunMainMessageLoopParts+0x6a 00007fff`0336e9c4 : 00000000`00000000 00000000`00000000 00000086`5d9a5db0 00000086`5d7df540 : chrome_7fff02490000!content::BrowserMainRunnerImpl::Run+0x17 00007fff`03852b1f : 00000000`00000000 00000086`5d9a5db0 00000086`5d7df540 00000000`00000000 : chrome_7fff02490000!content::BrowserMain+0xa8 00007fff`0385295b : 00000000`00000000 00000086`5d7df4c0 00000086`5d987f00 00000086`00000000 : chrome_7fff02490000!content::RunNamedProcessTypeMain+0x16b 00007fff`03851dc0 : 00000001`00000000 00000086`5d987f00 00000086`5d7df5e0 00000000`ffffffff : chrome_7fff02490000!content::ContentMainRunnerImpl::Run+0xcb 00007fff`030b7159 : 00000001`8ff42f6e 00007fff`15fdca04 00000086`5d7df649 00000086`5d7df5e0 : chrome_7fff02490000!content::ContentMain+0x30 *** WARNING: Unable to verify checksum for chrome.exe 00007ff7`fe7bedc8 : 00000086`00000000 00000086`5d984340 00000086`5d96b490 00000086`5d96b490 : chrome_7fff02490000!ChromeMain+0xa1 00007ff7`fe7bdf2c : 00000000`00000000 00000000`00000000 00000001`8ff42f6e 00000000`00000000 : chrome!MainDllLoader::Launch+0x350 00007ff7`fe7f0583 : 00007ff7`fe7f0500 00000000`0000000a 00007ff7`fe1b3000 00007ff7`fe1b3000 : chrome!wWinMain+0x154 *** WARNING: Unable to verify checksum for KERNEL32.DLL *** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNEL32.DLL - (Inline Function) : --------`-------- --------`-------- --------`-------- --------`-------- : chrome!invoke_main+0x21 00007fff`1f162d92 : 00007ff7`fe7f05d8 00000000`00000000 00000000`00000000 00000000`00000000 : chrome!__scrt_common_main_seh+0x117 00007fff`21779f64 : 00007fff`1f162d70 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34 . 0 Id: 1240.238 Suspend: 0 Teb: 00007ff7`fe1be000 Unfrozen RetAddr : Args to Child : Call Site 00007fff`1eb23757 : 00000086`5d7dc3b8 00000086`5d7dc400 00000086`5d7dc470 00007fff`057c7e39 : ntdll!ZwDelayExecution+0xa *** WARNING: Unable to verify checksum for chrome_elf.dll 00007fff`15fde038 : 00000000`00000000 00007fff`00000000 00000000`00000000 00000000`00000000 : KERNELBASE!SleepEx+0xa7 00007fff`1eb602ce : 00000000`00000000 00000000`00000000 00001081`443a4c6b 00000000`00000001 : chrome_elf!crashpad::CrashpadClient::StartHandler+0xcac 00007fff`21808992 : 00000000`00000000 00007fff`1eb60180 00000000`00000000 00000086`5d7df880 : KERNELBASE!UnhandledExceptionFilter+0x14e 00007fff`217f3f66 : 00000000`00000000 00000086`66905fb0 00000086`5d990a70 00000086`5d7df880 : ntdll!memset+0x852 00007fff`2180633d : 00000000`00000000 00000086`5d7dc7c0 00000086`5d7dcc90 00000086`5d7dc7c0 : ntdll!_C_specific_handler+0x96 00007fff`21783c00 : 00007fff`1f1f4960 00000086`5d7dcc90 00000000`00000000 00000000`00000000 : ntdll!_chkstk+0xfd 00007fff`2180544a : 00000000`00000020 00007fff`056ba010 00000086`6695d5b8 00000000`00000000 : ntdll!RtlWalkFrameChain+0x1560 00007fff`0351fec2 : 00000084`00000010 00000086`6695d5b8 00007fff`057c7e46 00000086`5d7dd5d0 : ntdll!KiUserExceptionDispatcher+0x3a 00007fff`03521037 : 00000001`90110023 00000086`6300d9a0 00000001`90110023 00007fff`035204a9 : chrome_7fff02490000!content::SyntheticGestureTargetBase::DispatchInputEventToPlatform+0x122 00007fff`03520ae9 : 00000001`90110023 00000000`00000000 00000000`00000000 00000000`00000000 : chrome_7fff02490000!content::SyntheticSmoothMoveGesture::ForwardTouchInputEvents+0x16b 00007fff`03521322 : 00000000`00000000 00000086`62ff50b0 00000086`5d7dd990 00000086`5d7dd9b8 : chrome_7fff02490000!content::SyntheticSmoothMoveGesture::ForwardInputEvents+0xad 00007fff`0351f360 : 00000086`667809a0 00000086`5d7dda40 00000086`00000000 00000086`5d7dd990 : chrome_7fff02490000!content::SyntheticSmoothScrollGesture::ForwardInputEvents+0x42 00007fff`03569d9b : 00000001`00000000 00000001`90110023 00000086`667809a0 00000086`6664a090 : chrome_7fff02490000!content::SyntheticGestureController::Flush+0xc8 00007fff`035750d6 : 00000001`90110023 00000086`5d7def01 00000000`00000000 00000086`627840e8 : chrome_7fff02490000!content::RenderWidgetHostImpl::FlushInput+0x37 00007fff`02f86796 : 00000086`00000000 00000086`6664a0d0 00000086`627a2950 00000086`5d7deff8 : chrome_7fff02490000!content::RenderWidgetHostViewAura::OnBeginFrame+0x2a 00007fff`025b4425 : 00000086`6664a090 00000086`66672460 00000000`00000001 00000086`5d7deff8 : chrome_7fff02490000!cc::DelayBasedBeginFrameSource::OnTimerTick+0x256 00007fff`025b4425 : 00000003`00000000 00000086`5d9b82f8 00000086`5d7deff8 0000bcdd`3c59eb57 : chrome_7fff02490000!base::internal::Invoker<base::internal::BindState<void (__cdecl base::CancelableCallback<void __cdecl(void)>::*)(void)const __ptr64,base::WeakPtr<base::CancelableCallback<void __cdecl(void)> > >,void __cdecl(void)>::Run+0x35 Seems like this is related to input. Lan, can you take a look?
,
Oct 4 2016
oshima@ fixed the windows high-DPI related issues in this Cl https://codereview.chromium.org/2373253004/ This should be fixed, can you please check it again?
,
Oct 4 2016
Thanks! Browser crash issue is gone. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by zh...@chromium.org
, Oct 3 2016