Comment #2 on issue 3881 by [email protected]: GC marking invariant
fails when OutOfLineConstantPool is enabled
https://code.google.com/p/v8/issues/detail?id=3881
Whenever a reference to a heap object is written, the write barrier (or
something with equivalent functionality) must be invoked. It seems that
that's what's missing in this case; as Ross notes (in 3. above) the code
object rather than the constant pool is made grey, even though the code
object is unchanged whereas the OOLCP has been modified.
So I think the right fix would be to teach RecordCodeTargetPatch() about
OOLCPs, to make sure the GC is properly notified about the CP modification.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
