github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 03:33:36 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

In the background, it OutOfMemoryError'd after the device resumed from being idle. #2262

New Issue
Open
opened 2025-11-26 23:13:37 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 23:13:37 -06:00
Owner
Copy Link

Originally created by @RokeJulianLockhart on GitHub (Jun 22, 2025).

Steps To Reproduce

All I did was unlock my device. Evidently, BW was active in the background.

Expected Result

It shouldn't have crashed.

Actual Result

FATAL EXCEPTION: DefaultDispatcher-worker-1
Process: com.x8bit.bitwarden, PID: 5541
java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 8 free bytes and 8B until OOM, target footprint 268435456, growth limit 268435456
	at java.util.HashMap$EntrySet.iterator(HashMap.java:1107)
	at java.time.format.Parsed.resolveFields(Parsed.java:281)
	at java.time.format.Parsed.resolve(Parsed.java:259)
	at java.time.format.DateTimeParseContext.toResolved(DateTimeParseContext.java:331)
	at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2056)
	at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1952)
	at java.time.ZonedDateTime.parse(ZonedDateTime.java:593)
	at com.bitwarden.core.data.serializer.ZonedDateTimeSerializer.deserialize(SourceFile:3)
	at com.bitwarden.core.data.serializer.ZonedDateTimeSerializer.deserialize(SourceFile:1)
	at nd.s.p(Unknown Source:282)
	at hd.a.deserialize(Unknown Source:140)
	at nd.s.p(Unknown Source:282)
	at ic.i.q(Unknown Source:29)
	at com.bitwarden.network.model.SyncResponseJson$Cipher$Login$$serializer.deserialize(SourceFile:1)
	at com.bitwarden.network.model.SyncResponseJson$Cipher$Login$$serializer.deserialize(SourceFile:2)
	at nd.s.p(Unknown Source:282)
	at ic.i.q(Unknown Source:29)
	at com.bitwarden.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SourceFile:1)
	at com.bitwarden.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SourceFile:2)
	at nd.s.p(Unknown Source:282)
	at md.c.a(Unknown Source:28)
	at m8.k.invokeSuspend(Unknown Source:27)
	at yc.a.resumeWith(Unknown Source:7)
	at Wc.L.run(Unknown Source:114)
	at dd.b.run(Unknown Source:126)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [v0{Cancelling}@4afc5cc, Dispatchers.Unconfined]

Additional Context

I wasn't doing anything that should cause this. The device was previously idle.

Build Version

  1. versionName=2025.5.0

  2. versionCode=20269

What server are you connecting to?

US

Environment Details

  1. #!/usr/bin/env sh
adb shell getprop | grep \
	-e "ro.build.version.release" \
	-e "ro.build.product"         \
	-e "ro.build.display.id"

  2. [ro.build.version.release]: [14]
[ro.build.product]: [FP5]
[ro.build.display.id]: [FP5.UT2P.B.122.20250422​​]

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @RokeJulianLockhart on GitHub (Jun 22, 2025). ### Steps To Reproduce All I did was unlock my device. Evidently, BW was active in the background. ### Expected Result It shouldn't have crashed. ### Actual Result <blockquote> ~~~YAML FATAL EXCEPTION: DefaultDispatcher-worker-1 Process: com.x8bit.bitwarden, PID: 5541 java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 8 free bytes and 8B until OOM, target footprint 268435456, growth limit 268435456 at java.util.HashMap$EntrySet.iterator(HashMap.java:1107) at java.time.format.Parsed.resolveFields(Parsed.java:281) at java.time.format.Parsed.resolve(Parsed.java:259) at java.time.format.DateTimeParseContext.toResolved(DateTimeParseContext.java:331) at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2056) at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1952) at java.time.ZonedDateTime.parse(ZonedDateTime.java:593) at com.bitwarden.core.data.serializer.ZonedDateTimeSerializer.deserialize(SourceFile:3) at com.bitwarden.core.data.serializer.ZonedDateTimeSerializer.deserialize(SourceFile:1) at nd.s.p(Unknown Source:282) at hd.a.deserialize(Unknown Source:140) at nd.s.p(Unknown Source:282) at ic.i.q(Unknown Source:29) at com.bitwarden.network.model.SyncResponseJson$Cipher$Login$$serializer.deserialize(SourceFile:1) at com.bitwarden.network.model.SyncResponseJson$Cipher$Login$$serializer.deserialize(SourceFile:2) at nd.s.p(Unknown Source:282) at ic.i.q(Unknown Source:29) at com.bitwarden.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SourceFile:1) at com.bitwarden.network.model.SyncResponseJson$Cipher$$serializer.deserialize(SourceFile:2) at nd.s.p(Unknown Source:282) at md.c.a(Unknown Source:28) at m8.k.invokeSuspend(Unknown Source:27) at yc.a.resumeWith(Unknown Source:7) at Wc.L.run(Unknown Source:114) at dd.b.run(Unknown Source:126) Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [v0{Cancelling}@4afc5cc, Dispatchers.Unconfined] ~~~ </blockquote> ### Additional Context I wasn't doing anything that should cause this. The device was previously idle. ### Build Version 1. `versionName=2025.5.0` 1. `versionCode=20269` ### What server are you connecting to? US ### Environment Details 1. ~~~sh #!/usr/bin/env sh adb shell getprop | grep \ -e "ro.build.version.release" \ -e "ro.build.product" \ -e "ro.build.display.id" ~~~ 1. > ~~~YAML > [ro.build.version.release]: [14] > [ro.build.product]: [FP5] > [ro.build.display.id]: [FP5.UT2P.B.122.20250422​​] > ~~~ ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:13:37 -06:00
GiteaMirror commented 2025-11-26 23:13:38 -06:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Jun 22, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-22905

@bitwarden-bot commented on GitHub (Jun 22, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22905
GiteaMirror commented 2025-11-26 23:13:38 -06:00
Author
Owner
Copy Link

@rmcdowell-bitwarden commented on GitHub (Jun 23, 2025):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you would be able to provide the version of Android and your device model, it would be greatly appreciated. Additionally, if you have more information that can help us, please add it below.

Thanks!

@rmcdowell-bitwarden commented on GitHub (Jun 23, 2025): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you would be able to provide the version of Android and your device model, it would be greatly appreciated. Additionally, if you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 23:13:38 -06:00
Author
Owner
Copy Link

@RokeJulianLockhart commented on GitHub (Jun 23, 2025):

If you would be able to provide the version of Android and your device model, it would be greatly appreciated.

@rmcdowell-bitwarden, a Fairphone 5. The AOSP version number, and the distribution's build identifier, are already included in the environment section.

Additionally, if you have more information that can help us, please add it below.

In retrospect, it might be related to https://github.com/bitwarden/android/issues/5412#issue-3169569962.

@RokeJulianLockhart commented on GitHub (Jun 23, 2025): > If you would be able to provide the version of Android and your device model, it would be greatly appreciated. @rmcdowell-bitwarden, a [Fairphone 5][1]. The AOSP version number, and the distribution's build identifier, are already included in the environment section. > Additionally, if you have more information that can help us, please add it below. In retrospect, it *might* be related to https://github.com/bitwarden/android/issues/5412#issue-3169569962. [1]: https://www.wikidata.org/w/index.php?title=Q122070914&oldid=2362479558#firstHeading:~:text=Random%20Lexeme-,Fairphone%205,-5G%20(Q122070914)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2262
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?