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
We finish the NativeActivity, which is the proper thing to do. Albeit the framework will do it for us in case we don't exist cleanly, but that shouldn't happen.
Finishing the nativeActivity makes the zygote forked process where the app lives to be killed, so no memory leaks are possible here, until I miss something.
Do you have a test case that shows how an anormal exist would lead to memory leaks?
native层没有看到lua层对jni调用统计的代码, 那么在lua虚拟机异常停止后, 在lua层比如self.env[0]FindClass申请到的内存会不会得不到释放从而导致泄漏?
The text was updated successfully, but these errors were encountered: