Hi Daryl, On Sun, Sep 23, 2018 at 4:15 PM 'Daryl Haresign' via v8-users < v8-users@googlegroups.com> wrote:
> What kind of handles are you using? We have seen similar issues (v8 > reporting objects that have already been collected) when using kFinalizer > weak persistent handles. For us we were not making use of the kFinalizer > feature (never resurrecting weak handles) so we simply switched to > kParameter to avoid the issue. > I'm not using finalizers. I read your previous e-mails and I think your situation is different from mine. In your situation, V8 is tracing an object that was already collected. In my situation, V8 is tracing a perfectly live object, but it is prematurely collecting objects reachable *through* the live object. The whole point of tracing is to find out what handles are transitively reachable, but V8 seems occasionally to collect those handles before it has actually done the requisite tracing. > The embedder heap tracer is only ever called on the main thread so there > are no threading concerns. In that case it must be parallel scavenges collecting my handles concurrently with the heap tracer running on the main thread. But, I have a scavenge callback as I described which should mark all weak handles as active. Is there something else needed? -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.
