NEW152738
Changing prototypes should cache the new structure.
https://bugs.webkit.org/show_bug.cgi?id=152738
Summary Changing prototypes should cache the new structure.
Keith Miller
Reported 2016-01-05 11:04:35 PST
Currently, when a programmer changes the prototype of their object we allocate a new structure every time even if they use the same prototype every time. Not only does this use linear additional memory if they do it to every object they allocate but it also perniciously causes all the code these objects touch to become megamorphic.
Attachments
Keith Miller
Comment 1 2016-01-20 12:07:54 PST
Whoever looks at this should consider fixing caching the structure for bound functions when the prototype is null.
Note You need to log in before you can comment on or make changes to this bug.