Report c1d21d2d8385aea9 is a crash in which PostTask() is invoked on a null TaskRunner.  This is caused by the calling content::RenderThreadImpl failing to Start() a media thread. Stack for the crash is:

0x62c88e8c	(chrome_child.dll -task_runner.cc:44 )	base::TaskRunner::PostTask(base::Location const &,base::OnceCallback<void >)
0x6508de9c	(chrome_child.dll -gpu_video_accelerator_factories_impl.cc:92 )	content::GpuVideoAcceleratorFactoriesImpl::GpuVideoAcceleratorFactoriesImpl(scoped_refptr<gpu::GpuChannelHost>,scoped_refptr<base::SingleThreadTaskRunner> const &,scoped_refptr<base::SingleThreadTaskRunner> const &,scoped_refptr<ui::ContextProviderCommandBuffer> const &,bool,bool,mojo::InterfacePtrInfo<media::mojom::VideoEncodeAcceleratorProvider>)
0x6508dcfe	(chrome_child.dll -gpu_video_accelerator_factories_impl.cc:64 )	content::GpuVideoAcceleratorFactoriesImpl::Create(scoped_refptr<gpu::GpuChannelHost>,scoped_refptr<base::SingleThreadTaskRunner> const &,scoped_refptr<base::SingleThreadTaskRunner> const &,scoped_refptr<ui::ContextProviderCommandBuffer> const &,bool,bool,mojo::InterfacePtrInfo<media::mojom::VideoEncodeAcceleratorProvider>)
0x65047188	(chrome_child.dll -render_thread_impl.cc:1591 )	content::RenderThreadImpl::GetGpuFactories()
0x6510a2ba	(chrome_child.dll -peer_connection_dependency_factory.cc:213 )	content::PeerConnectionDependencyFactory::CreatePeerConnectionFactory()
0x6510a04e	(chrome_child.dll -peer_connection_dependency_factory.cc:140 )	content::PeerConnectionDependencyFactory::GetPcFactory()
0x6510a93a	(chrome_child.dll -peer_connection_dependency_factory.cc:341 )	content::PeerConnectionDependencyFactory::CreatePeerConnection(webrtc::PeerConnectionInterface::RTCConfiguration const &,blink::WebLocalFrame *,webrtc::PeerConnectionObserver *)
0x650fcac3	(chrome_child.dll -rtc_peer_connection_handler.cc:1336 )	content::RTCPeerConnectionHandler::Initialize(blink::WebRTCConfiguration const &,blink::WebMediaConstraints const &)
0x65d4115a	(chrome_child.dll -RTCPeerConnection.cpp:577 )	blink::RTCPeerConnection::RTCPeerConnection(blink::ExecutionContext *,blink::WebRTCConfiguration const &,blink::WebMediaConstraints,blink::ExceptionState &)
0x65d403f0	(chrome_child.dll -RTCPeerConnection.cpp:511 )	blink::RTCPeerConnection::Create(blink::ExecutionContext *,blink::RTCConfiguration const &,blink::Dictionary const &,blink::ExceptionState &)
0x65c9bed3	(chrome_child.dll -V8RTCPeerConnection.cpp:1664 )	blink::V8RTCPeerConnection::constructorCallback(v8::FunctionCallbackInfo<v8::Value> const &)
0x62e6d70f	(chrome_child.dll -api-arguments.cc:29 )	v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo *)
0x639dcccd	(chrome_child.dll -builtins-api.cc:107 )	v8::internal::`anonymous namespace'::HandleApiCallHelper<1>
0x639dca84	(chrome_child.dll -builtins-api.cc:133 )	v8::internal::Builtin_Impl_HandleApiCall
0x62e6d3aa	(chrome_child.dll -builtins-api.cc:125 )	v8::internal::Builtin_HandleApiCall(int,v8::internal::Object * *,v8::internal::Isolate *)
...

Possibly the user's machine is out of memory, preventing the new thread from starting?