Skip to content

[Bug] VC 39 crashes, with an ANR and Java trace, when observing 102 MiB TIFFs. #1593

Open
Open
[Bug] VC 39 crashes, with an ANR and Java trace, when observing 102 MiB TIFFs.#1593
Assignees
zhanghai
Labels
bugSomething isn't working

Description

@beedell-roke
beedell-roke
opened on Jul 23, 2026

When I attempt to even observe some TIFFs (in /storage/emulated/0/Download/):

PowerShell 7.6.3-0-ga1994c19a0badf524d714cacffe7986c5c8613c6
PS /run/user/1000/32892c93_5ee3_4cad_987f_578fe1242351/storage/emulated/0/Download> lsd --tree --long --date '+%Y-%m-%dT%H:%M:%S%:z' --depth 1 | grep .tif |  bat --pager=none
─────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
     │ STDIN
─────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1 │ .rw-rw----. beedell.roke_julian_lockhart beedell.roke_julian_lockhart 102 MB 2026-07-23T18:51:11+01:00 ├── 20260723T185100.tif
   2 │ .rw-rw----. beedell.roke_julian_lockhart beedell.roke_julian_lockhart 102 MB 2026-07-23T19:14:46+01:00 ├── 20260723T191446.tif
   3 │ .rw-rw----. beedell.roke_julian_lockhart beedell.roke_julian_lockhart 102 MB 2026-07-23T19:18:30+01:00 ├── 20260723T191830.tif
   4 │ .rw-rw----. beedell.roke_julian_lockhart beedell.roke_julian_lockhart 102 MB 2026-07-23T19:20:17+01:00 ├── 20260723T192016.tif
─────┴───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

…via adb shell monkey -p me.zhanghai.android.files 1, versionCode=39 crashes:

screen-20260723-235044.mp4

The traces are:

  • 2026-07-23 19:40:46.571 10266 13300 13311 me.zhanghai.android.files AndroidRuntime: FATAL EXCEPTION: binder:13300_2
2026-07-23 19:40:46.571 10266 13300 13311 me.zhanghai.android.files AndroidRuntime: Process: me.zhanghai.android.files, PID: 13300
2026-07-23 19:40:46.571 10266 13300 13311 me.zhanghai.android.files AndroidRuntime: java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw an exception; no stack trace available
2026-07-23 19:40:46.573 10266 13300 13313 me.zhanghai.android.files AndroidRuntime: FATAL EXCEPTION: binder:13300_3
2026-07-23 19:40:46.573 10266 13300 13313 me.zhanghai.android.files AndroidRuntime: Process: me.zhanghai.android.files, PID: 13300
2026-07-23 19:40:46.573 10266 13300 13313 me.zhanghai.android.files AndroidRuntime: java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw an exception; no stack trace available
  • 2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ANR in me.zhanghai.android.files (me.zhanghai.android.files/.filelist.FileListActivity)
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: PID: 13300
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: Reason: Input dispatching timed out (b9a86dc me.zhanghai.android.files/me.zhanghai.android.files.filelist.FileListActivity (server) is not responding. Waited 5000ms for MotionEvent).
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: Parent: me.zhanghai.android.files/.filelist.FileListActivity
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ErrorId: c168d0bd-5f60-4eff-aad8-667576562229
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: Frozen: false
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: Load: 8.12 / 7.82 / 6.71
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- Output from /proc/pressure/memory -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: some avg10=0.57 avg60=0.67 avg300=0.56 total=257538360
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: full avg10=0.16 avg60=0.23 avg300=0.17 total=93960810
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- End output from /proc/pressure/memory -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- Output from /proc/pressure/cpu -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: some avg10=11.92 avg60=9.42 avg300=8.14 total=3358151524
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- End output from /proc/pressure/cpu -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- Output from /proc/pressure/io -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: some avg10=1.15 avg60=0.78 avg300=1.35 total=829044208
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: full avg10=0.36 avg60=0.30 avg300=0.68 total=550693353
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: ----- End output from /proc/pressure/io -----
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: CPU usage from 7799ms to -1ms ago (2026-07-23 19:40:32.036 to 2026-07-23 19:40:39.835):
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   141% 13300/me.zhanghai.android.files: 77% user + 63% kernel / faults: 2178548 minor 265 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   45% 1749/system_server: 31% user + 13% kernel / faults: 20998 minor 24 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   36% 9462/com.android.providers.calendar: 19% user + 17% kernel / faults: 1831 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   19% 10865/com.f0x1d.logfox: 12% user + 7.4% kernel / faults: 9029 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   14% 13055/org.fossify.calendar: 7.1% user + 7.5% kernel / faults: 1330 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   14% 1577/surfaceflinger: 10% user + 4.3% kernel / faults: 61 minor 1 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   6.4% 1433/vendor.qti.hardware.display.composer-service: 4.3% user + 2% kernel / faults: 201 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3.3% 5110/com.google.android.providers.media.module: 1.6% user + 1.6% kernel / faults: 1296 minor 46 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3% 25175/com.android.launcher3: 2.1% user + 0.8% kernel / faults: 1518 minor 49 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.9% 24676/com.google.android.gms.persistent: 1.9% user + 1% kernel / faults: 3276 minor 59 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: 43% TOTAL: 22% user + 18% kernel + 0.5% iowait + 1.3% irq + 0.3% softirq
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: CPU usage from 33ms to 482ms later (2026-07-23 19:40:39.868 to 2026-07-23 19:40:40.316):
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   110% 13300/me.zhanghai.android.files: 57% user + 52% kernel / faults: 32557 minor 1 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     55% 13313/binder:13300_3: 27% user + 27% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     44% 13303/Signal Catcher: 33% user + 11% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   59% 1749/system_server: 14% user + 45% kernel / faults: 1324 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     45% 13488/AnrAuxiliaryTas: 14% user + 30% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     4.7% 13485/AnrMainProcessD: 0% user + 4.7% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.3% 2752/SensorService: 2.3% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.3% 3094/binder:1749_6: 0% user + 2.3% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.3% 13486/AnrConsumer: 0% user + 2.3% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   24% 2805/com.loudtalks: 4.9% user + 19% kernel / faults: 541 minor 2017 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     12% 2955/Profile Saver: 4.9% user + 7.3% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     4.9% 5991/DefaultDispatch: 0% user + 4.9% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.4% 3035/Firebase Backgr: 0% user + 2.4% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.4% 5398/DefaultDispatch: 0% user + 2.4% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   11% 1567/audioserver: 7% user + 4.7% kernel / faults: 9 minor 13 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     9.4% 2520/FastMixer: 4.7% user + 4.7% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.3% 2582/AudioOut_4D: 2.3% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   10% 10865/com.f0x1d.logfox: 8% user + 2.6% kernel / faults: 215 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.6% 10881/DefaultDispatch: 2.6% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.6% 10950/DefaultDispatch: 2.6% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     2.6% 11196/DefaultDispatch: 2.6% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   6.9% 1371/android.hardware.audio.service: 2.3% user + 4.6% kernel / faults: 8 minor 2 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     6.9% 12399/writer: 0% user + 6.9% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   7.4% 24676/com.google.android.gms.persistent: 3.7% user + 3.7% kernel / faults: 5 minor 3 major
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     3.7% 13468/highpool[4960]: 3.7% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:     3.7% 24774/GlobalScheduler: 3.7% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.2% 607/logd: 0% user + 2.2% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.2% 720/tombstoned: 0% user + 2.2% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.3% 1221/netd: 0% user + 2.3% kernel / faults: 12 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.3% 1900/cnss_diag: 2.3% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   2.4% 3047/com.android.systemui: 2.4% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3.1% 14658/com.life360.android.safetymapd: 3.1% user + 0% kernel / faults: 2 minor
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3.4% 19558/kworker/u16:0-ufs_clkscaling_0: 0% user + 3.4% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3.4% 19823/kworker/u16:17-wmi_rx_diag_event_work_: 0% user + 3.4% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:   3.8% 27589/kworker/u16:9-memlat_wq: 0% user + 3.8% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager:  +0% 13496/i.android.files: 0% user + 0% kernel
2026-07-23 19:40:42.227 1000 1749 13486 com.fp5.iris ActivityManager: 45% TOTAL: 17% user + 22% kernel + 3.1% iowait + 1.9% irq + 0.5% softirq
2026-07-23 19:40:42.231 1000 1749 13486 com.fp5.iris ActivityManager: Completed ANR of me.zhanghai.android.files in 2415ms, latency 1ms

However, via cmd activity start --user 0 -a android.intent.action.VIEW -n com.google.android.documentsui/com.android.documentsui.files.FilesActivity -f 0 com.google.android.documentsui, I am able to:

Image

Activity

  1. zhanghai
    self-assigned this
    on Jul 24, 2026
  2. zhanghai
    added
    bugSomething isn't working
    on Jul 24, 2026

  3. zhanghai commented on Jul 24, 2026

    @zhanghai
    zhanghai
    on Jul 24, 2026
    Owner

    Sounds like an issue with thumbnail loading, which is handled by the coil library and isn't supposed to result in OOM.

  4. beedell-roke commented on Jul 24, 2026

    @beedell-roke
    beedell-roke
    on Jul 24, 2026
    Author

    @zhanghai, are you able to transfer it to Coil's issue tracker, or would you rather report it there, or should I?

  5. zhanghai commented on Jul 24, 2026

    @zhanghai
    zhanghai
    on Jul 24, 2026
    Owner

    I don't think there's a way to "transfer" issues (or at least I don't know). I think you can try reporting it to Coil, linking to https://github.com/zhanghai/MaterialFiles/blob/master/app/src/main/java/me/zhanghai/android/files/coil/PathAttributesFetcher.kt for how this app is currently fetching the thumbnail. If they can find out the issue directly that's great, but if they ask us to update the app to latest Coil and retest I'm afraid I won't have time for that lately because I'm too busy with my day job.

  6. beedell-roke commented on Jul 24, 2026

    @beedell-roke
    beedell-roke
    on Jul 24, 2026
    Author

    @zhanghai, one can transfer, if they've permissions to in both repositories. Otherwise, I can close this as a duplicate of an issue in their repository, like coil-kt/coil/issues/1349. However, I'll wait until they respond, until you are able to diagnose.

  7. zhanghai commented on Jul 25, 2026

    @zhanghai
    zhanghai
    on Jul 25, 2026
    Owner

    Wow, didn't know that. But I don't have any special permission to Coil repo so I assume I can't transfer anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions