V8 started to call to EmbedderHeapTracer during incremental marking steps that happen on allocation.
This could mean that there is C++ stack sitting on top of entering V8. Any chance that there are C++ objects holding traced V8 references that cannot be found by the EmbedderHeapTracer? E.g., this could happen when a C++ object is only reachable from stack without a proper stack scanning mechanism. The CL landed <https://chromium-review.googlesource.com/c/v8/v8/+/1350992> here. -Michael On Tue, Jan 15, 2019 at 3:01 AM 'Kenton Varda' via v8-users < v8-users@googlegroups.com> wrote: > Hi v8-users, > > Upon upgrading to V8 7.2, we're seeing GC collecting objects more > aggressively than before. It looks like we have another bug with our GC > integration, as we're occasionally seeing objects collected that should be > reachable using EmbedderHeapTracer. > > I'm trying to isolate the issue (so far I haven't been able to reproduce > outside of prod). But, meanwhile, are there any big changes to GC tracing > in 7.2 that might hint at what I'm getting wrong? The release blog post > didn't seem to mention anything: https://v8.dev/blog/v8-release-72 > > -Kenton > > -- > -- > v8-users mailing list > v8-users@googlegroups.com > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
