Comment #5 on issue 4335 by [email protected]: large google maps
performance regression in chrome canary (version 46)
https://code.google.com/p/v8/issues/detail?id=4335
@#3 the current hack for notifying that a non standard element appeared on
the prototype chain is conflated with requires-slow-elements, which is also
triggered by that limit. ICs don't check their prototype chain dynamically,
so we need to flush all keyed store ICs through a heap walk whenever such
an element might have appeared. In this case, unlike the other 4 paths, we
don't know whether the target is a prototype. So adding the element forces
a heap walk, which is utterly expensive and unwanted.
--
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.
