Fixed
Status Update
No update yet.
Comments
he...@gmail.com
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
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
vi...@google.com
vi...@google.com
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.
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.
wa...@gmail.com
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).
wa...@gmail.com
Here you are. It's a brief example which crashes on my Nexus.
Hope it was helpful
Hope it was helpful
na...@gmail.com
I would try it in Froyo but I have not received the upgrade yet.
he...@gmail.com
Comment has been deleted.
he...@gmail.com
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.
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.
[Deleted User] <[Deleted User]>
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.
Anyway, I am very pleased and grateful for the help.
he...@gmail.com
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.
r3...@gmail.com
Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38d20944 in tid 7589
li...@gmail.com
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 28045 (Studio:Socket)
bu...@gmail.com
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x34643120618b in tid 19406 (xample.letschat), pid 19406 (xample.letschat)
he...@gmail.com
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 16986 (EventThread), pid 15809
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? User Interface, Display, or Rendering issue
When did this happen?
Jun 17, 2022 01:34 GMT+02:00
What steps would let us observe this issue?
1. Open an audio player music, like YouTube Music.
2. Play some music. You can stop it now if you want to ;)
3. Swipe down from the top to access the notification shade. Now swipe down one more time to expand the Quick Tile and media player UI.
What did you expect to happen?
The media player UI isn't cut off at the bottom.
What actually happened?
The media player UI is cut off at the bottom.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
Additional comments
This is a follow-up issue for
This bug was supposedly fixed already (which was stated back in December 2021). But another form of this bug has persisted for over 2 months already!
Please make sure that this time you'll fix it for good!
Debugging information
Google Play services
com.google.android.gms
Version 221820044 (22.18.20 (190400-451484765))
System App (Updated)
Android System WebView
com.google.android.webview
Version 500512533 (102.0.5005.125)
System App (Updated)
Network operator: Telekom.de
SIM operator: Telekom.de
Filed by Android Beta Feedback. Version (Updated): 2.26-betterbug.external_20220504_RC03
To learn more about our feedback process, please visit