It'll be helpful to have a crash report id.

Update: 

Crash ID 77dba25e-fdba-4954-bb0b-43cc26aafd61 (Server ID: 1ba75ea700000000)

Deleted: Expec_Result.mov 5.0 MB

Expec_Result.mov 5.0 MB Download

+alexclarke based on the top frames in the crash report.

Please find the below bisect information,

https://chromium.googlesource.com/chromium/src/+log/79ef9d88a30ff239eb6c4ccad2195eef7b45b545..1f6acfe7dd08165baad36302b4388248e2854936?pretty=fuller&n=10000

Suspecting Commit# 8bf066cc7d7529342fd260e5bf3d98a97c6b133f
Suspecting Review URL# https://codereview.chromium.org/2474073005

@pfeldman -- Could you please look into the issue, kindly re-assign if it is not related to your changes.

Adding RBD as this is a recent Regression.
Just to update, able to reproduce this issue on Windows, Linux (56.0.2913.0) and Mac (56.0.2913.3).

Thank You.

Providing Stack Trace for the Crash ID - 1ba75ea700000000
Stack Trace ::
=========
Thread 0 CRASHED [EXC_BAD_ACCESS / KERN_INVALID_ADDRESS @ 0x00000018 ] MAGIC SIGNATURE THREAD
Stack Quality78%Show frame trust levels
0x00000001065823ac	(Google Chrome Framework -webthread_base.cc:32 )	blink::scheduler::WebThreadBase::TaskObserverAdapter::DidProcessTask(base::PendingTask const&)
0x0000000106577ec9	(Google Chrome Framework -task_queue_manager.cc:253 )	blink::scheduler::TaskQueueManager::DoWork(base::TimeTicks, bool)
0x0000000103c887c8	(Google Chrome Framework -callback.h:47 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x0000000103cabf95	(Google Chrome Framework -message_loop.cc:413 )	base::MessageLoop::RunTask(base::PendingTask*)
0x0000000103cac26b	(Google Chrome Framework -message_loop.cc:422 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask)
0x0000000103cac79c	(Google Chrome Framework -message_loop.cc:554 )	base::MessageLoop::DoDelayedWork(base::TimeTicks*)
0x0000000103caebf8	(Google Chrome Framework -message_pump_mac.mm:306 )	base::MessagePumpCFRunLoopBase::RunWork()
0x0000000103ca1279	(Google Chrome Framework + 0x0186d279 )	base::mac::CallWithEHFrame(void () block_pointer)
0x0000000103cae653	(Google Chrome Framework -message_pump_mac.mm:278 )	base::MessagePumpCFRunLoopBase::RunWorkSource(void*)
0x00007fff94eaea00	(CoreFoundation + 0x00080a00 )	__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
0x00007fff94ea0b8c	(CoreFoundation + 0x00072b8c )	__CFRunLoopDoSources0
0x00007fff94ea01be	(CoreFoundation + 0x000721be )	__CFRunLoopRun
0x00007fff94e9fbd7	(CoreFoundation + 0x00071bd7 )	CFRunLoopRunSpecific
0x00007fff9446bb28	(Foundation + 0x00090b28 )	-[NSRunLoop(NSRunLoop) runMode:beforeDate:]
0x0000000103caf25d	(Google Chrome Framework -message_pump_mac.mm:580 )	base::MessagePumpNSRunLoop::DoRun(base::MessagePump::Delegate*)
0x0000000103caea9b	(Google Chrome Framework -message_pump_mac.mm:210 )	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
0x0000000103cc9dd2	(Google Chrome Framework -run_loop.cc:35 )	base::RunLoop::Run()
0x000000010777a62e	(Google Chrome Framework -renderer_main.cc:198 )	content::RendererMain(content::MainFunctionParams const&)
0x000000010383708c	(Google Chrome Framework -content_main_runner.cc:776 )	content::ContentMainRunnerImpl::Run()
0x0000000103836315	(Google Chrome Framework -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x00000001024375ab	(Google Chrome Framework -chrome_main.cc:97 )	ChromeMain
0x00000001023ffda9	(Google Chrome Helper -chrome_exe_main_mac.c:85 )	main
0x00007fff9238f5c8	(libdyld.dylib + 0x000035c8 )	start
0x00007fff9238f5c8	(libdyld.dylib + 0x000035c8 )	start

Thank You.

That stack trace might be due to: https://bugs.chromium.org/p/chromium/issues/detail?id=660427

It would be great if we can land a fix/revert ASAP, since this is really blocking the Dev release.

Thank you!

Just re-read #5. If it's still happening in 56.0.2913.0 then it's probably not the same thing as https://bugs.chromium.org/p/chromium/issues/detail?id=660427

Users experienced this crash on the following builds:

Mac Canary 56.0.2913.3 -  172.81 CPM, 89 reports, 73 clients (signature blink::scheduler::WebThreadBase::TaskObserverAdapter::DidProcessTask)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

I hit this or something similar on my own build at 56.0.2914.0 (64-bit) ff0a4a3f4f165290c3da7902a67d98434a49e7e3, Ubuntu 14.04:

[122220:122220:1108/150616:ERROR:selection_owner.cc(192)] SelectionClear
Received signal 11 <unknown> 000000000000
#0 0x7fc51753d897 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#1 0x7fc5176a2330 <unknown>
#2 0x7fc51152e5a7 blink::scheduler::WebThreadBase::TaskObserverAdapter::DidProcessTask()
#3 0x7fc51165af94 blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
#4 0x7fc51165957c blink::scheduler::TaskQueueManager::DoWork()
#5 0x7fc51753e836 base::debug::TaskAnnotator::RunTask()
#6 0x7fc51756ed4d base::MessageLoop::RunTask()
#7 0x7fc51756f0d8 base::MessageLoop::DeferOrRunPendingTask()
#8 0x7fc51756f4eb base::MessageLoop::DoWork()
#9 0x7fc517570d0e base::MessagePumpDefault::Run()
#10 0x7fc51756ea31 base::MessageLoop::RunHandler()
#11 0x7fc51759e210 base::RunLoop::Run()
#12 0x7fc5154668d5 content::RendererMain()
#13 0x7fc5155af4df content::RunZygote()
#14 0x7fc5155afce8 content::RunNamedProcessTypeMain()
#15 0x7fc5155b072b content::ContentMainRunnerImpl::Run()
#16 0x7fc5155af0a0 content::ContentMain()
#17 0x7fc517fbd16d ChromeMain
#18 0x7fc50dc89f45 __libc_start_main
#19 0x7fc517fbd049 <unknown>
[end of stack trace]
[122220:122220:1108/152335:ERROR:process_metrics_linux.cc(137)] opendir(/proc/0/task): No such file or directory

I think I hit it by reloading with dev tools open on a WebGL 2 conformance test I was in the middle of editing, but I haven't been able to repro.

If this is not the same crash, LMK.

Deleted: fullstack.txt 7.1 KB

fullstack.txt 7.1 KB View Download

Hm, my crash hits a DCHECK with a TODO(erg). So, ccing erg.

If you're talking about the SelectionClear DLOG, that's a clipboard thing that's purely in the browser process and doesn't appear to have anything to do with the renderer stack in #11.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6965123c13447fbeebc5824318af521dc682999d

commit 6965123c13447fbeebc5824318af521dc682999d
Author: pfeldman <pfeldman@chromium.org>
Date: Wed Nov 09 01:52:38 2016

PerformanceMonitor: do not leak performance objects through the monitor.

BUG= 663260 

Review-Url: https://codereview.chromium.org/2478363003
Cr-Commit-Position: refs/heads/master@{#430821}

[modify] https://crrev.com/6965123c13447fbeebc5824318af521dc682999d/third_party/WebKit/Source/core/frame/PerformanceMonitor.cpp
[modify] https://crrev.com/6965123c13447fbeebc5824318af521dc682999d/third_party/WebKit/Source/core/timing/Performance.cpp
[modify] https://crrev.com/6965123c13447fbeebc5824318af521dc682999d/third_party/WebKit/Source/core/timing/Performance.h

Issue 663323 has been merged into this issue.

Verified the fix manually as per the repro steps in C#0 on Windows-10,Mac OS 10.11.6 and Linux Ubuntu 14.04 on chrome version: 56.0.2914.0. This is working as intended. Hence adding the verified label.

Marking it as 'Verified'.