Correction : Issue is not seen on Linux OS.

Stack Trace:
-------------
Thread 0 (id: 5772) CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x0000044200001b87 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x000007fee26e1306	(chrome_child.dll -resource.cpp:67 )	blink::`anonymous namespace'::NotifyFinishObservers
0x000007fee26e2752	(chrome_child.dll -bind_internal.h:329 )	base::internal::Invoker<base::internal::BindState<void (*)(blink::HeapHashSet<blink::WeakMember<blink::ResourceFinishObserver>,WTF::MemberHash<blink::ResourceFinishObserver>,WTF::HashTraits<blink::WeakMember<blink::ResourceFinishObserver> > >),blink::HeapHashSet<blink::WeakMember<blink::ResourceFinishObserver>,WTF::MemberHash<blink::ResourceFinishObserver>,WTF::HashTraits<blink::WeakMember<blink::ResourceFinishObserver> > > >,void >::Run(base::internal::BindStateBase *)
0x000007fee14d9d12	(chrome_child.dll -task_annotator.cc:59 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x000007fee300598f	(chrome_child.dll -task_queue_manager.cc:531 )	blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue(blink::scheduler::internal::WorkQueue *,bool,blink::scheduler::LazyNow,base::TimeTicks *)
0x000007fee3004836	(chrome_child.dll -task_queue_manager.cc:329 )	blink::scheduler::TaskQueueManager::DoWork(bool)
0x000007fee2c1900c	(chrome_child.dll -bind_internal.h:295 )	base::internal::InvokeHelper<1,void>::MakeItSo<void ( gpu::GpuWatchdogThread::*const &)(bool),base::WeakPtr<gpu::GpuWatchdogThread> const &,bool const &>(void ( gpu::GpuWatchdogThread::*const &)(bool),base::WeakPtr<gpu::GpuWatchdogThread> const &,bool const &)
0x000007fee14d9d12	(chrome_child.dll -task_annotator.cc:59 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x000007fee148b94e	(chrome_child.dll -message_loop.cc:422 )	base::MessageLoop::RunTask(base::PendingTask *)
0x000007fee148bb61	(chrome_child.dll -message_loop.cc:433 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask)
0x000007fee148c447	(chrome_child.dll -message_loop.cc:540 )	base::MessageLoop::DoWork()
0x000007fee14daebc	(chrome_child.dll -message_pump_default.cc:33 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate *)
0x000007fee14ab543	(chrome_child.dll -run_loop.cc:111 )	base::RunLoop::Run()
0x000007fee317e118	(chrome_child.dll -renderer_main.cc:219 )	content::RendererMain(content::MainFunctionParams const &)
0x000007fee27e725e	(chrome_child.dll -content_main_runner.cc:411 )	content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *)
0x000007fee27e70a7	(chrome_child.dll -content_main_runner.cc:704 )	content::ContentMainRunnerImpl::Run()
0x000007fee27ec4d5	(chrome_child.dll -main.cc:469 )	service_manager::Main(service_manager::MainParams const &)
0x000007fee27e67b7	(chrome_child.dll -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const &)
0x000007fee23f9441	(chrome_child.dll -chrome_main.cc:109 )	ChromeMain
0x000000013faf5e62	(chrome.exe -main_dll_loader_win.cc:199 )	MainDllLoader::Launch(HINSTANCE__ *,base::TimeTicks)
0x000000013faf4fa2	(chrome.exe -chrome_exe_main_win.cc:268 )	wWinMain
0x000000013fb26dc2	(chrome.exe -exe_common.inl:253 )	__scrt_common_main_seh
0x7767652c	(kernel32.dll + 0x0001652c )	BaseThreadInitThunk
0x777ac520	(ntdll.dll + 0x0002c520 )	RtlUserThreadStart

Bisect Information:
--------------------
Using per revision bisect providing information below.

You are probably looking for a change made after 479238 (known good), but no later than 479239 (first known bad).

Change Log URL:
https://chromium.googlesource.com/chromium/src/+log/69f629975374d2ab911228a92af9a197d66d55b6..c33cb55a26113bb1a16fc85727360e0fea7e7c8b
 
Steven@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Since this is a recent regression observed on chrome latest dev M61 adding RB-Dev, please feel free to edit if this is not the case.

Thanks!

There is another bug filed for this issue as well:
crbug.com/733581

The suspected CL there is
https://chromium-review.googlesource.com/c/522185/

Duping to crbug/733581

https://chromium-review.googlesource.com/c/522185/ seems like a much more plausible culprit.