Fixed
Status Update
No update yet.
Comments
vi...@google.com
bo...@google.com
wd...@google.com
wd...@google.com
bi...@gmail.com
I'm also seeing this issue, specifically under low-memory conditions and only on a Nexus 5x running Nougat. I was trying to launch a camera intent from a fragment. I've attached my log as well.
se...@gmail.com
I'm seeing this crash too, specifically on build NBD90W of Android on the nexus 5x (october security patches). We're not using a camera intent, but we're using the camera API directly.
dt...@gmail.com
Oh, good point -- I, too, am running build NBD90W with the October 5 security patches.
[Deleted User] <[Deleted User]>
Same here and my app uses Google Maps and a few images. It only crashes upon exit. My device is also Nexus 5X w/ build number NBD90W.
ta...@gmail.com
I am on NBD90W as well.
ta...@gmail.com
I was the reporter for the question on Stackoverflow -- I'm definitely glad other people are having this issue. Hopefully it can be resolved!
bu...@gmail.com
Can you provide the below requested information to better understand the issue:
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please attach sample project to reproduce the issue.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please attach sample project to reproduce the issue.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
bu...@gmail.com
Seeing the same crash here, I am using Android 7 and Nexus 5x.
[Deleted User] <[Deleted User]>
I can't come up with a good example project and unfortunately, I cannot share my project publicly as a result of my company's NDA. But, here's the bug report from our app:
https://drive.google.com/file/d/0Bzu4wPnZXr0FaTFFejM2STFkVTA/view?usp=sharing
I shared the file with android-bugreport@google.com as well but it looks like the email failed to deliver.
In any case, I have a fragment in my application. When an activity uses the fragment (via supportFragmentManager), things work fine. But when another activity has the fragment contained in a TabAdapter, I get a crash around 80% of the time. I experience the crash whenever I background this fragment. It should be noted that the app uses very similar amounts of memory in both of these cases (~30Mb)
The issue certainly seems to be memory-related. When I background the fragment, I get the standard TRIM_MEMORY_UI_HIDDEN from onTrimMemory. But just a few seconds later, I get a TRIM_MEMORY_COMPLETE and the app is killed (see my previous log).
I shared the file with android-bugreport@google.com as well but it looks like the email failed to deliver.
In any case, I have a fragment in my application. When an activity uses the fragment (via supportFragmentManager), things work fine. But when another activity has the fragment contained in a TabAdapter, I get a crash around 80% of the time. I experience the crash whenever I background this fragment. It should be noted that the app uses very similar amounts of memory in both of these cases (~30Mb)
The issue certainly seems to be memory-related. When I background the fragment, I get the standard TRIM_MEMORY_UI_HIDDEN from onTrimMemory. But just a few seconds later, I get a TRIM_MEMORY_COMPLETE and the app is killed (see my previous log).
[Deleted User] <[Deleted User]>
[Comment deleted]
Description
Android Studio Version: 2021.3.1
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.11-9058569
HAXM / KVM Version: HVF 12.6.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 12.6
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 65536 MB
GPU:
Build Fingerprint:
AVD Details: Name: Pixel_5_API_33
CPU/ABI: arm64
Path: /Users/marikan/.android/avd/Pixel_5_API_33.avd
Target: google_apis [Google APIs] (API level 33)
Skin: 1080x2340
SD Card: 2G
AvdId: Pixel_5_API_33
PlayStore.enabled: false
avd.ini.displayname: Pixel 5 API 33
avd.ini.encoding: UTF-8
disk.dataPartition.size: 2G
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:3274126e0242a0d86339850416b0ce34
hw.device.manufacturer: Google
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2340
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSize: 1536
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images/android-33/google_apis/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google APIs
vm.heapSize: 512
Steps to Reproduce Bug:
Start emulator with "-timezone" parameter(e.g emulator -avd Pixel_5_API_33 -timezone Asia/Shanghai)
Issue is reproducible when API level of the emulator is set to 31+. When API level is 30 emulator works as expected
Expected Behavior:
Emulator starts with timezone set to provided parameter value
Observed Behavior:
Emulator ignores the parameter and starts with host devices timezone.