Because JVMCI uses nmethods in some non-standard ways the actions of the concurrent nmethod sweeper has triggered some unusual bugs with nmethod being in surprising states. The use of an nmethodLocker closed the most obvious problem of the nmethod being freed while still in use by JVMCI but it would be better if some sort of official handle was used that kept the nmethod alive while JVMCI was interacting with it.