[v8-users] Re: Fatal error during scavenge collection on Android armeabi-v7a

2025-05-04 Thread Kasper Isager Dalsgarð
I finally figured out what went wrong and it's almost embarrassing: The crash occurred specifically on single core machines as I was allocating a worker thread for each available core, but always subtracted 1 for the main thread. On single core machines this meant that no workers were allocated

[v8-users] Re: Fatal error during scavenge collection on Android armeabi-v7a

2025-05-03 Thread Kasper Isager Dalsgarð
Another colleague is now hitting this on a Linux machine running under KVM. I'm still no closer to figuring out where things go wrong; any input would be greatly appreciated. On Thursday, 15 August 2024 at 14:00:29 UTC+2 Kasper Isager Dalsgarð wrote: > After several attempts at debugging this,

[v8-users] Re: Fatal error during scavenge collection on Android armeabi-v7a

2024-08-15 Thread Kasper Isager Dalsgarð
After several attempts at debugging this, I *think* I've narrowed it down to the some sort of interaction with QEMU as it consistently happens when running V8 on an emulated Android device on both 32- and 64-bit architectures. On Thursday 7 March 2024 at 09:48:23 UTC+1 Kasper Isager Dalsgarð wr

[v8-users] Re: Fatal error during scavenge collection on Android armeabi-v7a

2024-03-07 Thread Kasper Isager Dalsgarð
A colleague of mine briefly hit the same assertion on Android arm64-v8a, but has since been unable to reproduce it. I still haven't been able to narrow down what triggers it. On Thursday 22 February 2024 at 12:07:22 UTC+1 Kasper Isager Dalsgarð wrote: > I'm consistently observing a crash on And