3 ms·
Wow, that must have been a lot of freaking work. Testing this must be nightmare, if you have on native pointer left the browser could essentially randomly crash
by nickik 13y ago
Wow, that must have been a lot of freaking work. Testing this must be nightmare, if you have on native pointer left the browser could essentially randomly crash.
Pretty cool stuff. I really want to see the performance changes the GC can get.
- venomsnake 13y agoIsn't that problem right in the domain of automated testing and static code analysis?
- evilpie 13y agoWe do both, but it's still very tideous. After a while the dynamic analysis only caught false postives (something on the stack looked like a pointer). The static analysis had to be updated when new potential hazardous cases became obvious. https://wiki.mozilla.org/Javascript:SpiderMonkey:ExactStackRooting https://wiki.mozilla.org/Javascript:SpiderMonkey:ExactStackR...
- AndrewDucker 13y agoYou've got a typo in your URL there - missing 'n' in 'rooting'
- mccr8 13y agoWork on generational GC has been proceeding in parallel with the exact rooting work. You can see what the current generational GC performance is on standard benchmarks like Octane by looking at the "Firefox (Ion, GGC)" line on http://arewefastyet.com/ http://arewefastyet.com/