tag 0 is supposed to be unused, but: 1. in the comments: > cannot use 0 as tag, breaks atomWriteBarrier This is ancient, and may or may not be true. 2. Object initialization can expose code to kUnusedAtomTag. See Bug 645673. How should we fix this bug? - we could renumber tags to make all of them be legal - we could clarify comments and add lots of tests.

The player sticks unmanaged pointers in avmplus::Hashtable's using raw (Atom) casts. That's the deal, its basically one place (SymbolClassTable). It also sticks RCObjects in hastable's using atomToGenericObject that I have a patch for to switch to GCHashtable that I haven't had time to land (its causing asserts from the newly stricter atomWriteBarrier).

Tamarin is a dead project now. Mass WONTFIX.

Tamarin isn't maintained anymore. WONTFIX remaining bugs.