Comment #2 on issue 3918 by [email protected]: JitCodeEvent::CODE_REMOVED is
the wrong thing
https://code.google.com/p/v8/issues/detail?id=3918
Poking more, I find that CODE_REMOVED can indeed be fired, but only for
code objects in the LO space. It's not fired for normal code objects.
It seems to me that this event is not useful for debugging or perf
profiling, as these use cases can treat an ADDED event as implying as many
REMOVED events as needed. Memory profiling is better done with other
tools, so probably CODE_REMOVED can itself be removed.
--
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.
