I can see my libgdx based activity is leaking, but I have no idea where it is referenced from.
It seems that LeakCanary doesn't have access to the debug information of the libgdx part of the app (probably since it's built as a separate module in the project).
Attaching a screenshot of the leak dump:
What can I do to get LeakCanary to know what's going on within the libgdx part of the code?
答案 0 :(得分:0)
行, 事实证明它不是一个缺失的堆栈跟踪(Gdx.app是活动,并且是它的唯一引用),并且它毕竟不是一个重要的泄漏。
一旦我开始新的libgdx活动,Gdx.app将被设置为它,旧的将被销毁,所以这不是什么大问题。
(不删除问题,因为其他人可能会无理地担心同样的泄漏)。