-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
android demo在荣耀50/60全系机型上出现native报错 #5721
Comments
麻烦试一下最新代码看看,可以看一下是不是所有的模型都这样 |
感谢回复,使用的是最新release/2.4的分支,换了其他模型均出现此现象 |
你好,我说的是dygraph分支的代码哈,这个分支的代码支持单独测试det,rec和cls模型 |
Since you haven't replied for more than 3 months, we have closed this issue/pr. |
遇到了同样的问题,在这里记录一下解决方案: 另外,只要先推理过一张大图,再推理预热小图就不会报错。 |
调大一次后,开发者模式下可以运行,结果打包后就又有闪退问题了,随后再次尝试开发者模式下运行,结果也是闪退,太离谱了 |
换成Google MLKit即可解决问题 |
Build fingerprint: 'HONOR/NTH-AN00/HNNTH:11/HONORNTH-AN00/4.2.0.193C00:user/release-keys'
ABI: 'arm64'
Predictor Worke >>> com.baidu.paddle.lite.demo.ocr <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x6e452fe000
x0 0000006e45275680 x1 0000000000000000 x2 0000000000067600 x3 0000006e452fe000
x4 0000006e45365680 x5 0000000000000004 x6 0000000000000060 x7 0000000000000100
x8 0000006e64d161e8 x9 0000000000000001 x10 0000006e45275680 x11 000000000000001e
x12 0000000000000100 x13 00000000000f0000 x14 000000000003c000 x15 0000006ee8635af0
x16 0000006e5ad7a850 x17 00000071c88de0c0 x18 0000000000000014 x19 0000000000000001
x20 0000006e43a15080 x21 0000000000000102 x22 0000000000000102 x23 0000000000000100
x24 0000000000000100 x25 0000000000000100 x26 0000000000000018 x27 0000000000000018
x28 0000000000000060 x29 0000006e64d13380
lr 0000006e5ab99ffc sp 0000006e64d12f50 pc 00000071c88de1c0 pst 0000000020001000
backtrace:
#00 pc 000000000004b1c0 /apex/com.android.runtime/lib64/bionic/libc.so (memset+256) (BuildId: 8a99910f553b2716882e4f24a6670330)
Upload PaddleOCR code #1 pc 0000000000119ff8 /data/app/~~dvsaA4ZiQz3L5TpebQmuQQ==/com.baidu.paddle.lite.demo.ocr-8JfD6wPVozyKVKe-_53SGA==/base.apk!libpaddle_light_api_shared.so (offset 0xb59000)
The text was updated successfully, but these errors were encountered: