The object memory
implications:
- write barrier: every pointer write into an object must be checked; if
- moified object is old; and
- oop written is young; and
- modified object is not in rooTable
then add modified object to rootTable
- perform a major collection whenever rootTable overflows
observations:
- most pointer writes are to the stack portion of the activeContext
- always make active Context a root when activating a new block or method
- use unchecked writes into active Context