Show Posts
1
NGUI 3 Support / Re: Odd crash. Any ideas?
« on: January 07, 2016, 09:06:29 PM »
We had this same trace on a crash, you can see a UIAnchor call in the middle.
For us it was triggered by the OnDestroy function in UIAnchor where it tries to de-reference the delegated method for onScreenResize.
This static delegate is assigned on Awake of every instance of UIAnchor and de-referenced on every Destroy.
We have multiple NGUI hierarchies being created / destroyed and after inspecting we found our game often ends up in a state where there is no referenced method and it appears that on quitting the app the attempt to de-reference the method throws the error.
I'm not sure why an exception is not thrown within the app (surely we were triggering the OnDestroy method while the delegate pointed to null in several other places though it didn't cause a problem). It only seems a problem when OnDestroy is triggered on app close. Not sure if that makes it a Unity or NGUI problem, for now we've had to tweak the NGUI code to handle this case.
In any case it seems NGUI should be changed to account for use of multiple instances of UIAnchor - a single static var is being used to track a state which should be per-instance, what do you think Aren? We're on current version NGUI btw.
For us it was triggered by the OnDestroy function in UIAnchor where it tries to de-reference the delegated method for onScreenResize.
This static delegate is assigned on Awake of every instance of UIAnchor and de-referenced on every Destroy.
We have multiple NGUI hierarchies being created / destroyed and after inspecting we found our game often ends up in a state where there is no referenced method and it appears that on quitting the app the attempt to de-reference the method throws the error.
I'm not sure why an exception is not thrown within the app (surely we were triggering the OnDestroy method while the delegate pointed to null in several other places though it didn't cause a problem). It only seems a problem when OnDestroy is triggered on app close. Not sure if that makes it a Unity or NGUI problem, for now we've had to tweak the NGUI code to handle this case.
In any case it seems NGUI should be changed to account for use of multiple instances of UIAnchor - a single static var is being used to track a state which should be per-instance, what do you think Aren? We're on current version NGUI btw.