WeakHandle<vm_class_loader_data> uses the OopStorageSet::vm_weak() OopStorage. This is not obvious from the name. In particular, it becomes problematic when new weak handles are created in other areas of the VM, using the same OopStorage. I don't want them to go under the vm_class_loader_data name, when they have nothing to do with that. It seems more intuitive to name them vm_weak_data, reflecting which OopStorage they are associated with.