MessageDigest not thread safe: Segmentation fault crash [36917827]

WAI

Bug

Status Update

No update yet.

Description

ur...@gmail.com

created issue #1

May 28, 2010 04:44PM

Hi,

I received this error output in my application. I do not find out why it
is happening and what behaviour makes application crash. I do not know how
to translate these traces.

I am using Android 2.1-update1 with a Nexus One.

Let me know if you need more info, please.

Thanks!

I/DEBUG ( 49): *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** ***
I/DEBUG ( 49): Build fingerprint:
'google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys'
I/DEBUG ( 49): pid: 2710, tid: 3087 >>> com.startapp.wallpaper.browser <<<
I/DEBUG ( 49): signal 11 (SIGSEGV), fault addr 00000014
I/DEBUG ( 49): r0 0011de28 r1 44934428 r2 000000a4 r3 00000000
I/DEBUG ( 49): r4 005ac1a8 r5 44934418 r6 0011de28 r7 44934428
I/DEBUG ( 49): r8 4689dda0 r9 42b5def4 10 42b5dee0 fp 0062cf60
I/DEBUG ( 49): ip 00000000 sp 4689dd78 lr ad215ec7 pc af55aaaa
cpsr 00000030
I/DEBUG ( 49): #00 pc 0005aaaa /system/lib/libcrypto.so
I/DEBUG ( 49): #01 pc 00015ec4 /system/lib/libnativehelper.so
I/DEBUG ( 49): #02 pc 0000ecb4 /system/lib/libdvm.so
I/DEBUG ( 49):
I/DEBUG ( 49): code around pc:
I/DEBUG ( 49): af55aa98 00051d38 fffe85d4 fffe8618 f8d0b510
I/DEBUG ( 49): af55aaa8 f8dcc000 47983014 bf00bd10 6803b510
I/DEBUG ( 49): af55aab8 b14b4604 b13b6a1b f0032102 b918fd79
I/DEBUG ( 49):
I/DEBUG ( 49): code around lr:
I/DEBUG ( 49): ad215eb4 fefaf7ff 9a079906 46071841 f7f64630
I/DEBUG ( 49): ad215ec4 6820ea9a 463a4629 f8d02302 4620c300
I/DEBUG ( 49): ad215ed4 462047e0 fdc2f7ff 81f0e8bd 41f0e92d
I/DEBUG ( 49):
I/DEBUG ( 49): stack:
I/DEBUG ( 49): 4689dd38 4689dda0
I/DEBUG ( 49): 4689dd3c ad039a65 /system/lib/libdvm.so
I/DEBUG ( 49): 4689dd40 0062cf60 [heap]
I/DEBUG ( 49): 4689dd44 00000001
I/DEBUG ( 49): 4689dd48 00000007
I/DEBUG ( 49): 4689dd4c 42b5df04
I/DEBUG ( 49): 4689dd50 4689dda0
I/DEBUG ( 49): 4689dd54 44934418 /dev/ashmem/mspace/dalvik-heap/2
(deleted)
I/DEBUG ( 49): 4689dd58 44934428 /dev/ashmem/mspace/dalvik-heap/2
(deleted)
I/DEBUG ( 49): 4689dd5c 0062cf60 [heap]
I/DEBUG ( 49): 4689dd60 00000000
I/DEBUG ( 49): 4689dd64 ad039bdb /system/lib/libdvm.so
I/DEBUG ( 49): 4689dd68 005ac1a8 [heap]
I/DEBUG ( 49): 4689dd6c 44934418 /dev/ashmem/mspace/dalvik-heap/2
(deleted)
I/DEBUG ( 49): 4689dd70 df002777
I/DEBUG ( 49): 4689dd74 e3a070ad
I/DEBUG ( 49): #00 4689dd78 005ac1a8 [heap]
I/DEBUG ( 49): 4689dd7c ad215ec7 /system/lib/libnativehelper.so
I/DEBUG ( 49): #01 4689dd80 4689ddc0
I/DEBUG ( 49): 4689dd84 00000000
I/DEBUG ( 49): 4689dd88 40019a90
/dev/ashmem/mspace/dalvik-heap/zygote/0 (deleted)
I/DEBUG ( 49): 4689dd8c 42b5df04
I/DEBUG ( 49): 4689dd90 4689dda0
I/DEBUG ( 49): 4689dd94 ad00ecb8 /system/lib/libdvm.so

Comments

[Deleted User] <[Deleted User]> #2May 28, 2010 09:23PM

Decoded stack trace:

pid: 2710, tid: 3087 >>> com.startapp.wallpaper.browser <<<
signal 11 (SIGSEGV), fault addr 00000014
r0 0011de28 r1 44934428 r2 000000a4 r3 00000000
r4 005ac1a8 r5 44934418 r6 0011de28 r7 44934428
r8 4689dda0 r9 42b5def4 10 42b5dee0 fp 0062cf60
ip 00000000 sp 4689dd78 lr ad215ec7 pc af55aaaa

Stack Trace:
RELADDR FUNCTION
FILE:LINE
0005aaaa EVP_DigestUpdate
/usr/local/google/buildbot/repo_clients/git_eclair-
release/external/openssl/crypto/evp/digest.c:213
v------> NativeCrypto_EVP_DigestUpdate
/usr/local/google/buildbot/repo_clients/git_eclair-release/dalvik/libcore/x-
net/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:346
00015ec4 NativeCrypto_EVP_DigestUpdate(_JNIEnv*, _jclass*, env_md_ctx_st*,
_jbyteArray*, int, int) /usr/local/google/buildbot/repo_clients/git_eclair-
release/dalvik/libcore/x-
net/src/main/native/org_apache_harmony_xnet_provider_jsse_NativeCrypto.cpp:346
0000ecb4 dvmPlatformInvoke
/usr/local/google/buildbot/repo_clients/git_eclair-
release/dalvik/vm/arch/arm/CallEABI.S:243

ur...@gmail.com <ur...@gmail.com> #3May 29, 2010 09:17AM

Thank you very much!

I think I fixed the error. Maybe it could be helpful for you too.

I was using a MessageDigest to digest lots of data arrays but I wasn't reseting the
instance. Check it out because it was crashing the application with a SIGSEV.

I hope it was helpful.

en...@google.com <en...@google.com> #4Jun 11, 2010 06:39AM

can you give us a small repeatable test case so we can find and fix the bug (or confirm that we've already fixed it --- much of that code has been rewritten in froyo).

ur...@gmail.com <ur...@gmail.com> #5Jun 11, 2010 11:26AM

Here you are. It's a brief example which crashes on my Nexus.

Hope it was helpful

deleted

Restricted

0 B

ur...@gmail.com <ur...@gmail.com> #6Jun 11, 2010 11:28AM

I would try it in Froyo but I have not received the upgrade yet.

en...@google.com <en...@google.com> #7Jun 11, 2010 09:31PM

your example still crashes in froyo. i'll investigate.

(fyi, if you ever want to test against the current release but don't have a device, you can download the SDK and test in the emulator. the SDK is released before any devices get the corresponding code.)

en...@google.com <en...@google.com> #8Jun 11, 2010 10:22PM

Status: Won't Fix (Intended Behavior)

the problem in the sample code is that MessageDigest is stateful and thus not thread-safe. you can't use a MessageDigest simultaneously from multiple threads and get meaningful results. rather than return nonsense, Android goes one step further and actually crashes. we could add synchronization, but that would slow down correct code, and cause incorrect code to silently return wrong results. so it's arguably better to keep the current behavior and crash.

i will update the documentation to (a) explicitly mention thread safety and (b) include an example showing how to use MessageDigest correctly, but i don't think i can usefully change the behavior.

ur...@gmail.com <ur...@gmail.com> #9Jun 11, 2010 11:21PM

I understand my code is wrong due to MessageDigest methods aren't synchronized but it must never stop the program with a SIGSEV. It is very difficult to debug. So I would reconsider the solution.

Anyway, I am very pleased and grateful for the help.

sa...@gmail.com <sa...@gmail.com> #10Nov 7, 2019 10:28AM

D/AccessibilityManager: current package=com.activa.one.singlerecognition, accessibility manager mIsFinalEnabled=false, mOptimizeEnabled=false, mIsUiAutomationEnabled=false, mIsInterestedPackage=false
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x28 in tid 25330 (nglerecognition)
Process 25330 terminated.

because of this fatal error app crashes I am very pleased and grateful for the help.

[Deleted User] <[Deleted User]> #11Dec 10, 2020 10:15AM

Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38d20944 in tid 7589

ke...@gmail.com <ke...@gmail.com> #12Jan 26, 2021 01:09AM

A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 28045 (Studio:Socket)

sm...@gmail.com <sm...@gmail.com> #13Sep 30, 2021 11:28AM

A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x34643120618b in tid 19406 (xample.letschat), pid 19406 (xample.letschat)

[Deleted User] <[Deleted User]> #14Jun 23, 2023 03:50AM

any update ?

de...@gmail.com <de...@gmail.com> #15Jan 16, 2024 10:52AM

Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 16986 (EventThread), pid 15809

ig...@gmail.com <ig...@gmail.com> #16Jul 25, 2024 02:06PM

Hello.
I am getting a crash every time I scroll a part of a page.

--------- beginning of crash
2024-07-25 09:55:39.062 3888-5141 libc A Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20 in tid 5141 (RenderThread), pid 3888
2024-07-25 09:55:39.203 9387-9387 crash_dump64 pid-9387 A crash_dump.cpp:485] failed to attach to thread 5141, already traced by 4020 (/data/data/lldb/bin/lldb-server)
2024-07-25 09:55:39.278 3888-5141 libc A crash_dump helper failed to exec, or was killed
2024-07-25 09:55:39.863 9394-9394 I Late-enabling -Xcheck:jni
2024-07-25 09:55:39.898 9394-9394 I Using CollectorTypeCMC GC.
2024-07-25 09:55:39.899 9394-9394 W Unexpected CPU variant for x86: x86_64.
Known variants: atom, sandybridge, silvermont, goldmont, goldmont-plus, tremont, kabylake, default