Hi, In V8 13.2 and 13.3 we see wasm isolates external memory usage blowing up sometimes (up to gigabytes). Under V8 13.1 the same code would never ever use more than 80-100MB The issue doesn't happen every time for the same wasm bytecode. It doesn't even reproduce locally. But some significant percentage of the time it does happen. This has only started happening in 13.2, what are we missing? Should we be enabling/disabling some flags? It also seems that 13.3 is significantly worse in terms of error rate. The problem happens under "--liftoff-only". We use pointer compression but not sandbox. We've tried enabling --turboshaft-wasm in 13.1 and the problem did not reproduce. Has anything changed that we need to adapt to? Would really appreciate your help!
-- -- 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/CAO44E%2BBCXF5WZd-R0QJ%2B8dfqqy6yLzDfuU-KyKvsoD4f0N9MTA%40mail.gmail.com.
