I maintain bindings for V8 for the R programming language. We run into a difficult problem: applications that run WASM seem to be random crashing on Windows 2025 with the following error:
[mutex.cc : 2600] RAW: Check waitp->thread->waitp == nullptr failed: waiting when shouldn't be This error originates in abseil <https://github.com/abseil/abseil-cpp/blob/b2574e9da3b999f51bc8d007479c0af8b56fbffd/absl/synchronization/mutex.cc#L2600>. I tested this both with V8 14.0.365.4 and 14.1.146.11. Strangely it never happens on Windows 2022; but we found in other instances as well that Windows 2025 has become more strict/sensitive about memory and threading bugs. Besides being non deterministic, what makes this difficult to reproduce is that we have to compile with gcc from mingw-w64 (we use mingw-w64-v8 <https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-v8/PKGBUILD> on msys2). Any hint to which component of v8 could be related to this? -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CABFfbXseoZK2MSuWxWSOWGNiSwvBiu5uhp%3Dg%3DtbDF16-0DObFA%40mail.gmail.com.
