-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppDelegate deconstructor is not called on Android #14110
Comments
@rynkowsg , all it's totally true. |
@FrankStain |
AppDelegate object and all its members are never released. As a solution I propose to use static unique_ptr that could destroy it at the end of the application. Issue: cocos2d#14110
AppDelegate object and all its members are never released. As a solution I propose to use static unique_ptr that could destroy it at the end of the application. Issue: cocos2d/cocos2d-x#14110
@FrankStain, In my organisation I applied this fix couple months ago and it works perfectly. |
@rynkowsg , Frankly, i had never thought in such direction. Also |
* Remove AppDelegate memory leak from Android projects AppDelegate object and all its members are never released. As a solution I propose to use static unique_ptr that could destroy it at the end of the application. Issue: #14110 * Correct code style in Android main.cpp files - removed redundant headers (reduced dependencies) - removed redundant code - corrected code style
My changes have been merged. I'm going to close the issue. |
I used at
AppDelegate
's deconstructor a log, and it was not printed.I was looking and I found that
AppDelegate
object is created on the heap and probably it is not released.Please look on the Android's
main.cpp
:Does it should be like this?
The text was updated successfully, but these errors were encountered: