Gerrit Code Review
chromium-review.googlesource.com
November 5, 2025 at 10:09 PM
Sorry for the loss @jenmsft.bsky.social ... Absolutely understand the heartbreak 💔
October 18, 2025 at 10:43 PM
Sorry for the loss @jenmsft.bsky.social ... Absolutely understand the heartbreak 💔
I think ideally we'd be able to have it on but we're not going to break users. That always comes first.
October 16, 2025 at 10:51 PM
I think ideally we'd be able to have it on but we're not going to break users. That always comes first.
No decision has been made yet on whether it'll be on by default, only that we're a step closer now to making it possible. I think if we ever did we'd have to provide a release distribution that has it off as well as on, letting users decide. But it's too early to say.
October 16, 2025 at 10:50 PM
No decision has been made yet on whether it'll be on by default, only that we're a step closer now to making it possible. I think if we ever did we'd have to provide a release distribution that has it off as well as on, letting users decide. But it's too early to say.
It's going to take some time if we can safely Have point of compression on by default at any time. But without IsolateGroups it is absolutely impossible.
October 16, 2025 at 10:05 PM
It's going to take some time if we can safely Have point of compression on by default at any time. But without IsolateGroups it is absolutely impossible.
This is part of the mechanism that we use in cloudflare workers to enable having multiple isolates within a single process but still have pointer compression enabled. And we contributed it to V8 so that we could have it for other things like node.js as well.
October 16, 2025 at 10:03 PM
This is part of the mechanism that we use in cloudflare workers to enable having multiple isolates within a single process but still have pointer compression enabled. And we contributed it to V8 so that we could have it for other things like node.js as well.
The other part of this is it should cut in half the amount of heap memory your applications are currently using, so if you are at 4 GB now, your applications should only use 2 GB of heap with this enabled. So it gives you a lot more headroom to grow. And you can leverage worker threads to get more.
October 16, 2025 at 10:02 PM
The other part of this is it should cut in half the amount of heap memory your applications are currently using, so if you are at 4 GB now, your applications should only use 2 GB of heap with this enabled. So it gives you a lot more headroom to grow. And you can leverage worker threads to get more.
The IsolateGroup addition makes it possible for us to get around the 4 GB limit. Basically each isolate group has its own cage that is limited to 4 GB. But each worker thread will be in its own cage, so there is no more 4 GB limit for the entire process.
October 16, 2025 at 10:01 PM
The IsolateGroup addition makes it possible for us to get around the 4 GB limit. Basically each isolate group has its own cage that is limited to 4 GB. But each worker thread will be in its own cage, so there is no more 4 GB limit for the entire process.