###@###.### pointed out that since the removal of the _next field
from symbolOops (as a consequence of the introduction of class data sharing),
the size computation for symbolOops has been off by a word and there has been a
mismatch in the Serviceability Agent's size computation for these objects. The
SA is currently unable to walk the permanent generation in 1.5 builds. This must
be fixed, preferably by fixing the VM's size computation.