[lazerg]

When a lazy ghost finishes initializing, zend_lazy_object_init() deletes its info entry, and that is where the initializer gets released. The hash removes the entry before running its destructor, so any destructor fired by releasing the initializer (here a gc_collect_cycles() in the initializer's __destruct) no longer sees the stale info and is allowed to call resetAsLazyGhost() on the object. zend_lazy_object_init() then returns an object that is lazy again, and zend_lazy_object_get_properties() asserts. ReflectionClass::markLazyObjectAsInitialized() has the same problem and ends up returning without a value or an exception.

The fix releases the initializer before the info entry is deleted in both places, so a reset at that point throws "Can not reset an object while it is being initialized", the same as during the initializer call. Lazy proxies already release their initializer this way.

Fixes #24715

[lazerg]

The LINUX_X32_DEBUG_ZTS failure is a timeout in ext/pcntl/tests/002.phpt, which this change does not touch.