Crashed: GC_is_marked for IOS

I'm experiencing an iOS crash issue in v1.11.0 ~ v1.11.2. Looking at the changelog for v1.11.3~v1.11.4, it's clear this bug likely hasn't been fixed.
I am using Unity 2022.3.62f2 and using Incremental GC. I would be grateful if you could confirm.

Below are the error details (using v1.11.2)

Crashed: tokio-runtime-worker
0 UnityFramework 0x1989e3c GC_is_marked + 242 (mark.c:242)
1 UnityFramework 0xbd5cc00 push_ephemerons(GC_ms_entry*, GC_ms_entry*) + 662 (BoehmGC.cpp:662)
2 UnityFramework 0x1987c5c GC_mark_some + 405 (mark.c:405)
3 UnityFramework 0x1987260 GC_stopped_mark + 833 (alloc.c:833)
4 UnityFramework 0x1986cf8 GC_try_to_collect_inner + 580 (alloc.c:580)
5 UnityFramework 0x19828b0 GC_init + 1309 (misc.c:1309)
6 UnityFramework 0x1982fb8 GC_generic_malloc_inner + 175 (malloc.c:175)
7 UnityFramework 0x1982cc4 GC_gcj_malloc + 147 (gcj_mlc.c:147)
8 UnityFramework 0xbd90140 il2cpp::vm::Object::NewAllocSpecific(Il2CppClass*) + 82 (Object.cpp:82)
9 UnityFramework 0xbda87dc il2cpp::vm::Thread::Attach(Il2CppDomain*) + 153 (Thread.cpp:153)
10 UnityFramework 0xbda877c il2cpp::vm::ScopedThreadAttacher::ScopedThreadAttacher() + 15 (ScopedThreadAttacher.cpp:15)
11 UnityFramework 0x3e4e67c ReversePInvokeWrapper_NativeHttpHandlerCore_OnReceive_m4158FC4532267FECFEEF3143942621775F2DA961 + 3964 (Cysharp.Net.Http.YetAnotherHttpHandler.cpp:3964)
12 UnityFramework 0xb8e4dbc yaha_native::binding::yaha_request_begin::_$u7b$$u7b$closure$u7d$$u7d$::h2b7e6909f781913f + 5980
13 UnityFramework 0xb8e0720 tokio::runtime::task::harness::Harness$LT$T$C$S$GT$::poll::h7b92a6cd8b60b97c + 404984
14 UnityFramework 0xba47350 tokio::runtime::scheduler::multi_thread::worker::Context::run_task::h7380ac8088d2521f + 596
15 UnityFramework 0xba44d5c tokio::runtime::context::scoped::Scoped$LT$T$GT$::set::he6d0c6622b0923ca + 640
16 UnityFramework 0xba4129c tokio::runtime::context::runtime::enter_runtime::hc727493226e38c0b + 516
17 UnityFramework 0xba4708c tokio::runtime::scheduler::multi_thread::worker::run::hbd73f82e5169ac5a + 104
18 UnityFramework 0xba501bc tokio::runtime::task::core::Core$LT$T$C$S$GT$::poll::h5323d7e8693b7ffc + 3652
19 UnityFramework 0xba25a34 tokio::runtime::task::harness::Harness$LT$T$C$S$GT$::poll::h3911bee5cfacc862 + 7076
20 UnityFramework 0xba388dc tokio::runtime::blocking::pool::Inner::run::h7cb65a1b877c1f56 + 1604
21 UnityFramework 0xba3b164 std::sys::backtrace::__rust_begin_short_backtrace::ha559214fb74c3691 + 192
22 UnityFramework 0xba3ba34 core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h902e9e781817c27d + 1864
23 UnityFramework 0xbad31f4 std::sys::pal::unix::thread::Thread::new::thread_start::h45a7f62b02ec0fe0 + 395 (mod.rs:395)
24 libsystem_pthread.dylib 0x444c _pthread_start + 136
25 libsystem_pthread.dylib 0x8cc thread_start + 8

Start by reproducing the iOS crash with Unity 2022.3.62f2, Incremental GC, and YetAnotherHttpHandler v1.11.2. Read the stack frames in mark.c, BoehmGC.cpp, Object.cpp, Thread.cpp, and Cysharp.Net.Http.YetAnotherHttpHandler.cpp, then compare behavior with v1.11.3 and v1.11.4. Done means determining whether the reported GC_is_marked crash is reproducible and whether those versions change the result.