Marcel Laverdet
Marcel Laverdet
@pkit sorry I'm not sure what you're asking? Do you mean you want to open a PR on nodejs?
I don't mind, the code is part of v8 now. It sounds like that's between you and the plv8 team if this is an issue for you on that platform.
It would never terminate before my patch, now it terminates eventually 🤷🏼♂️
Are you running into this super often? I do regret not picking a smaller chunk size but I'm not sure it's worth bringing the Chromium team into this again to...
I assume you're talking about setjmp & longjmp? Jumping over a non-trivial destructor is UB. I'm actually planning on locking the thread when the OOM handler and invoking some callback...
Just grep the v8 codebase for "~" or "std". There's are *lots* of non-trivial destructors and you *are* relying on UB. This is definitely an architectural problem in v8 but...
You're not just throwing away the topmost frame, you're also throwing away all the frames under it. Log a backtrace and you'll see that v8 has dozens of frames that...
Is this on Linux, or another operating system?
`cpuTime` on non-Linux systems is calculated by the difference in wall time between work start and work end in an isolate. This is, of course, strictly larger than the actual...
Your understanding seems correct to me. The improvement I mentioned would only be relevant to accessing `cpuTime` from the current isolate. So you do `await context.global.set('isolate', isolate)` and then from...