3 ms·
Yes, lazy copying tricks are employed, and some work round stack frames delayed until the stack is moved by the GC on the assumption most will not live that lon
by aardvark179 4y ago
Yes, lazy copying tricks are employed, and some work round stack frames delayed until the stack is moved by the GC on the assumption most will not live that long.
There was a lot of work done on debugging so standard Java debuggers work well.
- anonymousDan 4y agoThat's pretty cool! What about the blocking issue? Presumably also if you are using JNI all bets are off?
- aardvark179 4y agoIf you are using JNI then that puts a native frame on the stack and pins the virtual thread. Loom’s strategy works because we know what can be on the Java stack, and that nothing external points into it, but we don’t know that for native frames.