LemonStand Forum: Issue with Phpr_SecurityFramework and core:onUninitialize - LemonStand Forum

If you use core:onUninitialize and try to access some class which utilizes Phpr_SecurityFramework there's the potential for a race condition because destructors aren't called in any specific order. In this case, __destruct of the Phpr_SecurityFramework class is being called before my core:onUnitialize method. When Phpr_SecurityFramework::create() is called, it returns the reference to the instance, but Phpr_SecurityFramework->mode_descriptor no longer points to a valid mcrypt resource, resulting in a bunch of warnings being fired and data not being decrypted properly.

I believe the proper way to solve this would be to set self::$instance = null at the end of the destructor so if the class is needed again it will return a fresh class.

I'm bumping this because it's becoming an issue with more of my modules. Any thoughts on a fix?

Updating status to: Fixed (and published)

Phil, we published the fix. The event is now triggered with PHP's register_shutdown_function() function.

Thank you