有没有大佬帮我看看,为什么原生蓝牙插件脸上后,会在as中报weex错误,
在hb中不会,也不影响程序运行。
我现在有个长时间运行程序的需求,我不知道是不是这个原因导致我设备9小时左右会卡死
有没有大佬帮我看看,为什么原生蓝牙插件脸上后,会在as中报weex错误,
在hb中不会,也不影响程序运行。
我现在有个长时间运行程序的需求,我不知道是不是这个原因导致我设备9小时左右会卡死
俞19 (作者)
2025-02-21 08:08:45.030 16615-16771 st.dcloud.eliga est.dcloud.eliga I Starting a blocking GC Alloc
2025-02-21 08:08:45.030 16615-16771 st.dcloud.eliga est.dcloud.eliga I Starting a blocking GC Alloc
2025-02-21 08:08:45.037 16615-16771 st.dcloud.eliga est.dcloud.eliga I This is sticky GC, maxfree is 8388608 minfree is 2097152
2025-02-21 08:08:45.037 16615-16771 st.dcloud.eliga est.dcloud.eliga I Alloc young concurrent copying GC freed 1745(147KB) AllocSpace objects, 0(0B) LOS objects, 5% free, 427MB/451MB, paused 98us,15us total 6.547ms
2025-02-21 08:08:45.037 16615-16771 st.dcloud.eliga est.dcloud.eliga I Forcing collection of SoftReferences for 127MB allocation
2025-02-21 08:08:45.037 16615-16771 st.dcloud.eliga est.dcloud.eliga I Starting a blocking GC Alloc
2025-02-21 08:08:46.099 16615-16771 st.dcloud.eliga est.dcloud.eliga I This is non sticky GC, maxfree is 8388608 minfree is 2097152
2025-02-21 08:08:46.099 16615-16771 st.dcloud.eliga est.dcloud.eliga I Alloc concurrent copying GC freed 85(13KB) AllocSpace objects, 0(0B) LOS objects, 5% free, 427MB/451MB, paused 2.703ms,25us total 1.062s
2025-02-21 08:08:46.099 16615-16771 st.dcloud.eliga est.dcloud.eliga W Throwing OutOfMemoryError "Failed to allocate a 134217720 byte allocation with 25165824 free bytes and 84MB until OOM, target footprint 473941508, growth limit 536870912" (VmSize 26108248 kB)
2025-02-21 08:08:46.100 16615-16771 weex est.dcloud.eliga E callModuleMethod >>> invoke module:timer, method:setTimeout failed. java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at com.taobao.weex.bridge.MethodInvoker.invoke(SourceFile:1)
at com.taobao.weex.bridge.NativeInvokeHelper.invoke(SourceFile:40)
at com.taobao.weex.bridge.WXModuleManager.dispatchCallModuleMethod(SourceFile:2)
at com.taobao.weex.bridge.WXModuleManager.callModuleMethod(SourceFile:25)
at com.taobao.weex.bridge.WXBridgeManager.callModuleMethod(SourceFile:27)
at com.taobao.weex.bridge.WXBridgeManager.callNativeModule(SourceFile:59)
at com.taobao.weex.bridge.WXBridge.callNativeModule(SourceFile:40)
at com.taobao.weex.base.SystemMessageHandler.nativeRunWork(Native Method)
at com.taobao.weex.base.SystemMessageHandler.handleMessage(SourceFile:1)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:224)
at android.os.Looper.loop(Looper.java:318)
at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: java.lang.OutOfMemoryError: Failed to allocate a 134217720 byte allocation with 25165824 free bytes and 84MB until OOM, target footprint 473941508, growth limit 536870912
at dalvik.system.VMRuntime.newUnpaddedArray(Native Method)
at com.android.internal.util.ArrayUtils.newUnpaddedArray(ArrayUtils.java:84)
at com.android.internal.util.GrowingArrayUtils.insert(GrowingArrayUtils.java:140)
at android.util.SparseArray.put(SparseArray.java:281)
at com.taobao.weex.ui.module.WXTimerModule.postMessage(SourceFile:2)
at com.taobao.weex.ui.module.WXTimerModule.postOrHoldMessage(SourceFile:4)
at com.taobao.weex.ui.module.WXTimerModule.setTimeout(SourceFile:2)
at java.lang.reflect.Method.invoke(Native Method)
at com.taobao.weex.bridge.MethodInvoker.invoke(SourceFile:1)
at com.taobao.weex.bridge.NativeInvokeHelper.invoke(SourceFile:40)
at com.taobao.weex.bridge.WXModuleManager.dispatchCallModuleMethod(SourceFile:2)
at com.taobao.weex.bridge.WXModuleManager.callModuleMethod(SourceFile:25)
at com.taobao.weex.bridge.WXBridgeManager.callModuleMethod(SourceFile:27)
at com.taobao.weex.bridge.WXBridgeManager.callNativeModule(SourceFile:59)
at com.taobao.weex.bridge.WXBridge.callNativeModule(SourceFile:40)
at com.taobao.weex.base.SystemMessageHandler.nativeRunWork(Native Method)
at com.taobao.weex.base.SystemMessageHandler.handleMessage(SourceFile:1)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:224)
at android.os.Looper.loop(Looper.java:318)
at android.os.HandlerThread.run(HandlerThread.java:67)
俞19 (作者)
感觉是computed 一只运行,内存没释放?
computedConflist大概150ms执行一次
computed: {
...mapGetters(['getBtGroupSingle', 'getSnValue']),
computedStatelist() {
// console.log('this.statelist ',new Date().getTime());
if (!this.statelist) return [];
return this.statelist.map(item => ({
id: item.id().toString(16),
comment: item.comment(),
text: item.getText(),
unit: item.unit(),
value: item.getValue(),
raw: item
}));
},
computedConflist() {
if (!this.conflist) return [];
return this.conflist.map(item => ({
id: item.id().toString(16),
comment: item.comment(),
text: item.getText(),
unit: item.unit(),
value: item.getValue(),
raw: item
}));
},
formattedRamValue() {
const GROUP_SINGLE = this.getBtGroupSingle;
return this.ramp4 == 0 ?
GROUP_SINGLE.join(", ") :
GROUP_SINGLE.map(x => x.toString(16)).join(", ");
}
},