You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where the constructor for this object throws an exception, subsequent method calls on this object will attempt to call a null object.
I feel that the ProxyInitializer should be set to null after the object is initialized. This way other method calls will attempt to initialize the object again if the exception was caught elsewhere.
The text was updated successfully, but these errors were encountered:
This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes#8877).
Discussion
----------
Clear lazy loading initializer after the service is successfully initialized
Fixes#8875
Commits
-------
da73102 Clear lazy loading initializer after the service is successfully initialized
The current lazy loading code sets the initializer to null before the instance is initialized.
Code references RuntimeInstantiator (also in ProxyDumper):
In cases where the constructor for this object throws an exception, subsequent method calls on this object will attempt to call a null object.
I feel that the ProxyInitializer should be set to null after the object is initialized. This way other method calls will attempt to initialize the object again if the exception was caught elsewhere.
The text was updated successfully, but these errors were encountered: