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? Thanks! -- -- 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/da454b0c-4615-40be-b148-830cfc83ea1an%40googlegroups.com.
