3 ms·

Is this the equivalent work of Oilpan project for Chromium-Blink? https://groups.google.com/a/chromium.org/d/msg/blink-dev/59fb1FIirx0/u1EV00Ca5sgJ https://grou

by afsina 13y ago

Is this the equivalent work of Oilpan project for Chromium-Blink? https://groups.google.com/a/chromium.org/d/msg/blink-dev/59fb1FIirx0/u1EV00Ca5sgJ https://groups.google.com/a/chromium.org/d/msg/blink-dev/59f... Doc: https://docs.google.com/document/d/1y7_0ni0E_kxvrah-QtnreMlzCDKN3QP4BN1Aw7eSLfY/edit https://docs.google.com/document/d/1y7_0ni0E_kxvrah-QtnreMlz...

pcwalton 13y ago
No, Oilpan is different; it's a garbage collector for C++ objects, while exact rooting is for JS objects. Oilpan has more in common with the XPCOM cycle collector in purpose (although the approach is different), which Firefox has had for several years now but which WebKit has had no equivalent to.
- DannyBee 13y ago
  Right, and on the flip side, V8 has had a generational, incremental JS collector for quite a while :)
  - mccr8 13y ago
    For what its worth, it looks like v8 has had incremental GC since 2011 ( http://blog.chromium.org/2011/11/game-changer-for-interactive.html http://blog.chromium.org/2011/11/game-changer-for-interactiv... and generational GC for longer) while Firefox has had IGC since 2012 ( https://blog.mozilla.org/javascript/2012/08/28/incremental-gc-in-firefox-16/ https://blog.mozilla.org/javascript/2012/08/28/incremental-g... ).