On Thu, Jun 12, 2025 at 3:37 PM ClearScript Developers < clearscript...@gmail.com> wrote:
> Greetings! > > We've run into a new issue in V8 13.7 (upgrading from 13.5). In a > multi-isolate application, tearing down one isolate can trigger synchronous > activity in another – specifically, the posting of ReleasePooledChunksTask. > > Evidently, that happens because, by default, both isolates are in the same > group. Our understanding is that isolate groups are a new feature that > allows isolates to share certain resources, and that, unfortunately, is a > problem for us. In our case, isolates must remain... isolated. > > Setting up a dedicated group for each isolate appears to be possible, but > isolate groups require pointer compression, which we'd prefer to disable. > Even if we enabled it, pointer compression isn't supported on 32-bit > systems, which we still support. > > Can someone shed some light? Why do isolate groups require pointer > compression? How difficult would it be to remove that restriction? > > At this point V8 only officially supports a configuration with a single IsolateGroup. The concept of IsolateGroup was introduced by other embedders and as you wrote it's really for sharing a bunch of resources. E.g., read-only space, page pool, and at this point also a pointer compression cage. You could imagine an IsolateGroup without pointer compression -- at this point this is just not implemented. For maintenance and security reasons we can't accept any non-trivial patches for this area at this point as we cannot reliably test other configurations and ensure that they don't cause security problems down the line. -Michael -- -- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CAH%2BmL5CWjvnpqfYPvv_rdsmH6h-x4mWOtzqDCdPjLA%2BV0c4oQA%40mail.gmail.com.
