We're seeing some invoke crashers on some more exotic pages than usual on M69 Mac.

Tinder: http://shortn/_YpJt1qIVo5  200 clients / 480 crashers
Github: http://shortn/_1xNxL16wUZ   32 clients /  56 crashers

All crashers have the very same stack trace:

0x000000010db76879	(Google Chrome Framework -simulator.h:113 )	v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, bool, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, v8::internal::Handle<v8::internal::Object>, v8::internal::Execution::MessageHandling, v8::internal::Execution::Target)
0x000000010db765a7	(Google Chrome Framework -execution.cc:191 )	v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*)
0x000000010d8582d4	(Google Chrome Framework -api.cc:5250 )	v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*)
0x000000011129dd4e	(Google Chrome Framework -v8_script_runner.cc:407 )	blink::V8ScriptRunner::CallInternalFunction(v8::Isolate*, v8::Local<v8::Function>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*)
0x000000011207a9c9	(Google Chrome Framework -v8_script_runner.h:105 )	blink::ReadableStreamOperations::GetReader(blink::ScriptState*, blink::ScriptValue, blink::ExceptionState&)
0x0000000111a9455d	(Google Chrome Framework -body_stream_buffer.cc:395 )	blink::BodyStreamBuffer::CloseAndLockAndDisturb(blink::ExceptionState&)
0x0000000111a94b0b	(Google Chrome Framework -body_stream_buffer.cc:567 )	blink::BodyStreamBuffer::ReleaseHandle(blink::ExceptionState&)
0x0000000111a9494f	(Google Chrome Framework -body_stream_buffer.cc:224 )	blink::BodyStreamBuffer::StartLoading(blink::FetchDataLoader*, blink::FetchDataLoader::Client*, blink::ExceptionState&)
0x0000000112432eb7	(Google Chrome Framework -cache.cc )	blink::Cache::PutImpl(blink::ScriptState*, blink::HeapVector<blink::Member<blink::Request>, 0ul> const&, blink::HeapVector<blink::Member<blink::Response>, 0ul> const&, blink::ExceptionState&)
0x00000001124329c8	(Google Chrome Framework -cache.cc )	blink::Cache::put(blink::ScriptState*, blink::RequestOrUSVString const&, blink::Response*, blink::ExceptionState&)
0x00000001121ed66f	(Google Chrome Framework -v8_cache.cc:253 )	blink::V8Cache::putMethodCallback(v8::FunctionCallbackInfo<v8::Value> const&)
0x000000010d8b7897	(Google Chrome Framework -api-arguments-inl.h:95 )	v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*)
0x000000010d8b6d3c	(Google Chrome Framework -builtins-api.cc:110 )	v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments)
0x000000010d8b640a	(Google Chrome Framework -builtins-api.cc:140 )	v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*)

Assigning to current V8 stability sherrif to investigate, looks like an API / Blink issue though.