NativeScript / NativeScript/android
[Marking Mode: None]: Crash: Attempt to use cleared object reference
还没有人认领这个 Issue。
- 主要语言
- C++
- 星标
- 563
- 派生
- 144
- 平均合并
- 10 小时 46 分钟
- 30 天内合并 PR
- 14
描述
Please, provide the details below:
Via crashlytics we have been getting reports of crashes of the type
com.tns.NativeScriptException: Attempt to use cleared object reference id=48048(com.tns.NativeScriptException: Attempt to use cleared object reference id=48048
com.tns.Runtime.getJavaObjectByID(Runtime.java:893)
Did you verify this is a real problem by searching Stack Overflow and the other open issues in this repo?
Other closed bugs reference the same or similar issues (latest was closed for 3.0.0).
Please provide the following version numbers that your issue occurs with:
- CLI: 3.2.1
- Cross-platform modules: 3.2.0
- Runtime(s): 3.2.0
- Plugin(s):
-
- nativescript-angular: 4.4.1
-
- nativescript-fabric: 0.3.1
-
- nativescript-pro-ui: 3.2.0
-
- nativescript-google-maps-sdk: 2.3.3
Built using webpack (npm run ns-bundle --android --build-app --snapshot --clean --release)
Also using in app/package.json:
"android": {
"v8Flags": "--expose_gc",
"markingMode": "none"
}
Did the error happen while the app was being constructed? (buildtime error)
No
Did the error happen while the app was executing? (runtime error)
Yes, but I haven't reproduced it myself. Just numerous similar stack traces being sent via crashlytics/fabric.
e.g.
#0. Crashed: main: 0 0 0x0000000000000000
at .Error: com.tns.NativeScriptException: Attempt to use cleared object reference id=48048(com.tns.NativeScriptException: Attempt to use cleared object reference id=48048
com.tns.Runtime.getJavaObjectByID(Runtime.java:893)
com.tns.Runtime.callJSMethodNative(Native Method)
com.tns.Runtime.dispatchCallJSMethodNative(Runtime.java:1084)
com.tns.Runtime.callJSMethodImpl(Runtime.java:966)
com.tns.Runtime.callJSMethod(Runtime.java:953)
com.tns.Runtime.callJSMethod(Runtime.java:937)
com.tns.Runtime.callJSMethod(Runtime.java:929)
com.tns.gen.java.lang.Runnable.run(Runnable.java:10)
android.os.Handler.handleCallback(Handler.java:751)
android.os.Handler.dispatchMessage(Handler.java:95)
android.os.Looper.loop(Looper.java:154)
android.app.ActivityThread.main(ActivityThread.java:6780)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1496)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1386):1)
at . ... (repeats with slight differences)
full trace at https://pastebin.com/JEGTYrpx
Please tell us how to recreate the issue in as much detail as possible.
Unknown. Possibly random.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 com.tns.Runtime.getJavaObjectByID(Runtime.java:893) 和提供的 Crashlytics trace 开始;比较报告中的 runtime 版本和 Android 的 markingMode 配置。完成要求是提供一个可复现的案例,并为已清除的对象引用导致的崩溃提供经过验证的修复,但该 issue 没有提供复现步骤。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- android, cpp, java
- 领域
- mobile-dev
- Issue 类型
- 缺陷
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 15/100