-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Signal 11(SIGSEGV), Code 2(SEGV_ACCERR) #1440
Comments
Please provide Logs from MMKV. |
And symbolize your call stacks. |
MMKV Logs106 Stacksat com.tencent.mmkv.MMKV.encodeString(Native method) |
|
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x71f61ab22b
****** new tombstone parse success 2024-11-27 19:21:38(北京时间) ****** |
According to your call stacks it crashed inside
|
MMKV files |
According to the logs, I guess it crashed on loading the default MMKV instance, right? |
|
The file is corrupted. It is not the original make.default & make.default.crc file when your crash happens. |
The root cause is that your metafile (mmkv.default.crc) has the flag that AutoKeyExpire is enabled, but the data file (mmkv.default) is not actually in the format. Enabling auto-key-expiration is a breaking change API, once you enable it, the data file's format will change completely.
Can you provide a demo project that reproduces this problem, starting from the very beginning when mmkv.default is not auto-key-expire, and then auto-key-expire is turned on, and then it's corrupted? |
Thank you for your detailed explanation regarding the issue with the metafile and data file in MMKV. |
Note:
The language of MMKV
Java
The version of MMKV
v1.3.9
The platform of MMKV
The installation of MMKV
Maven
What's the issue?
Signal 11(SIGSEGV), Code 2(SEGV_ACCERR)
00 pc 000000000004d390 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#1 pc 000000000004cf54 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#2 pc 0000000000050070 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#3 pc 000000000004f7f0 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#4 pc 000000000004f4f8 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#5 pc 0000000000041090 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#6 pc 0000000000041278 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#7 pc 0000000000039b04 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/lib/arm64/libmmkv.so
#8 pc 00000000003f7e90 /data/app/~~L_ekTp14n5g64eXqslBD1A==/com.xxx.xxx-9fByeNZL54cd2P10Ej2uRw==/oat/arm64/base.odex (art_jni_trampoline+144)
at com.tencent.mmkv.MMKV.encodeString(Native method)
at com.tencent.mmkv.MMKV.encode(MMKV.java:11)
The text was updated successfully, but these errors were encountered: