Comment 6 for bug 1640542

After applying Chris’ patch (attached here for reference), I’m still seeing the renderer crash, but the trace is now different:

(gdb) bt
#0 0xf5c545f2 in oxide::ObjectBackedNativeHandler::NewInstance() ()
   from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#1 0xf5c56ffa in oxide::ScriptMessageManager::SendMessageInner(v8::FunctionCallbackInfo<v8::Value> const&) ()
   from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#2 0xf498c71a in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) ()
   from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#3 0xf49ef182 in 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) ()
   from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#4 0xf49ef63a in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) ()
   from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#5 0x4290a33c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)