Obsolete
Status Update
No update yet.
Comments
he...@gmail.com
vi...@google.com
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
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.
he...@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).
he...@gmail.com
Here you are. It's a brief example which crashes on my Nexus.
Hope it was helpful
Hope it was helpful
vi...@google.com
I would try it in Froyo but I have not received the upgrade yet.
vi...@google.com
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.)
(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.)
vi...@google.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.
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?
Apr 26, 2022 22:09 GMT+02:00
What steps would let us observe this issue?
1. Activate face-based Auto-rotate.
2. Open YouTube.
3. Start a video.
4. Very slowly turn the device from vertical angle to horizontal.
What did you expect to happen?
I expected the display to adjust to the angle of my face, so that it now displays the video in full screen in horizontal mode.
What actually happened?
It didn't change the angle mode...
How often has this happened?
Frequently
What was the effect of this issue on your device usage, such as lost time or work?
Moderate
Additional comments
This has been persistent negative behaviour since Android 12. Google, fix it already for Android 13 stable later this year! It's so embarrassing!
Debugging information
Google Play services
com.google.android.gms
Version 221215044 (22.12.15 (190400-439420056))
System App (Updated)
Android System WebView
com.google.android.webview
Version 495150733 (101.0.4951.7)
System App (Updated)
Network operator: Telekom.de
SIM operator: Telekom.de
Filed by Android Beta Feedback. Version (Updated): 2.25-betterbug.external_20220328_RC02
To learn more about our feedback process, please visit