Skip to content
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 native Crash #317

Closed
liuhongda opened this issue Aug 27, 2019 · 6 comments
Closed

Android native Crash #317

liuhongda opened this issue Aug 27, 2019 · 6 comments

Comments

@liuhongda
Copy link

SIGBUS(BUS_ADRERR):
#00 pc 00009bd2 /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#1 pc 00009b93 /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#2 pc 00009c4f /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#3 pc 00006b1d /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#4 pc 00006a4d /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#5 pc 000072e3 /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#6 pc 00002f99 /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/lib/arm/libmmkv.so [armeabi-v7a::c2da770998db3376193a87cb98aeefb6]
#7 pc 000c97d9 /data/app/com.tencent.weishi-9xe5NaoLfDV1Wj2DmmOikw==/oat/arm/base.odex (oatdata+821209) [armeabi::4892e19cd05c59aa41e8e9d3a6955789]
java:
com.tencent.mmkv.MMKV.putString(SourceFile:551)

@lingol
Copy link
Collaborator

lingol commented Aug 28, 2019

We shall chat on WeChat Work.

@lingol
Copy link
Collaborator

lingol commented Aug 28, 2019

Turns out this is the classic opening a MMKV in multi-process without setting MULTI_PROCESS_MODE problem.

@pengwei1024
Copy link

MULTI_PROCESS_MODE

Turns out this is the classic opening a MMKV in multi-process without setting MULTI_PROCESS_MODE problem.

Why not set MULTI_PROCESS_MODE as the default option?multi process execution is not easy to detect

@lingol
Copy link
Collaborator

lingol commented Nov 25, 2019

Because Multi-process mode doesn't come without cost. There's a flock, and flock costs time on each operation you make.

@pengwei1024
Copy link

I mean the default value is set to MULTI_PROCESS_MODE , People who are familiar with process operations and need extreme performance will be actively set to SINGLE_PROCESS_MODE,this can avoid many misuses

@lingol
Copy link
Collaborator

lingol commented Nov 25, 2019

I mean the default value is set to MULTI_PROCESS_MODE , People who are familiar with process operations and need extreme performance will be actively set to SINGLE_PROCESS_MODE,this can avoid many misuses

I DO know what you mean. And the answer is still the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants