I’ve noticed with the last 2-3 versions of the app (currently 0.0.69, nice); the app crashes 2/3rds of the time when returning to it from being in the background.

Open the app, switch to another app, switch back a couple min later and it closes then reopens as if you’d just started it for the first time today (losing whatever post you had open).

Curious if others are experiencing this?

Android 14, One UI 6.1

    • Darkassassin07@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      This appears daily for the last 2 weeks:

      Stacktrace

      java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.Class java.lang.Object.getClass()’ on a null object reference at androidx.compose.ui.graphics.layer.LayerManager.persistLayers(Unknown Source:118) at androidx.compose.ui.graphics.AndroidGraphicsContext$componentCallback$1$onTrimMemory$1.onPreDraw(Unknown Source:16) at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:1204) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4723) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:3288) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:11344) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1689) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1698) at android.view.Choreographer.doCallbacks(Choreographer.java:1153) at android.view.Choreographer.doFrame(Choreographer.java:1079) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1646) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:230) at android.os.Looper.loop(Looper.java:319) at android.app.ActivityThread.main(ActivityThread.java:8919) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

      END of stacktrace

      Thread info

      Name: main ID: 2 State: RUNNABLE Priority: 5 Thread group name: main Thread group parent: system Thread group active count: 32 Thread time: 0 hr 5 min, 5 sec

      END of thread info

      Device info

      Report ID: 14f3b073-a751-49aa-9a7b-222db9bf0e15 Device ID: 88a115ded4d03269 Application version: 69 Default launcher: com.sec.android.app.launcher Timezone name: Pacific Standard Time Timezone ID: America/Vancouver Version release: 14 Version incremental : A546WVLS7CXE1 Version SDK: 34 Board: s5e8835 Bootloader: A546WVLS7CXE1 Brand: samsung CPU ABIS 32: armeabi-v7a, armeabi CPU ABIS 64: arm64-v8a Supported ABIS: arm64-v8a, armeabi-v7a, armeabi Device: a54x Display: UP1A.231005.007.A546WVLS7CXE1 Fingerprint: samsung/a54xcs/a54x:14/UP1A.231005.007/A546WVLS7CXE1:user/release-keys Hardware: s5e8835 Host: SWDK6120 ID: UP1A.231005.007 Manufacturer: samsung Product: a54xcs Build time: 1715231961000 Build time formatted: 08-05-2024 22:19:21 Type: user Radio: A546WVLS7CXE1,A546WVLS7CXE1 Tags: release-keys User: dpi User IDs: N/A Is sustained performance mode supported: No Is in power save mode: No Is in interactive state: Yes Is ignoring battery optimizations: Yes Thermal status: STATUS_NONE Location power save mode: MODE_NO_CHANGE Is device idle: No Battery percentage: 91 Battery remaining time: 31-12-1969 16:00:00 Is battery charging: No Is device rooted: No CPU Model: N/A Number of CPU cores: 8 Up time with sleep: 509 hr 22 min, 56 sec Up time without sleep: 340 hr 53 min, 28 sec

      END of Device info

      Exit reasons

      Exit reason #1 Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 22-06-2024 10:50:05 END of exit reason #1

      Exit reason #2 Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 22-06-2024 06:08:27 END of exit reason #2

      Exit reason #3 Description: crash Importance: FOREGROUND Reason: CRASH Timestamp: 21-06-2024 19:44:57 END of exit reason #3

      END of exit reasons

      Application info

      App name: Jerboa Version code: 69 Version name: 0.0.69 Package name: com.jerboa Short package name: jerboa Flavor: N/A Signatures: nORRaWmGNmrBj18PL/p3svEr/s4= Is debuggable: No First installed: 27-09-2023 19:04:21 Last updated: 15-06-2024 01:37:51 Requested permissions: android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.READ_MEDIA_AUDIO, android.permission.READ_MEDIA_IMAGES, android.permission.READ_MEDIA_VIDEO, com.jerboa.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, android.permission.READ_MEDIA_VISUAL_USER_SELECTED Default prefs: N/A Default prefs: N/A

      END of Application info

      Currently running foreground/background processes

      N/A

      END of running foreground/background processes info

  • GolfNovemberUniform@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    5 months ago

    It’s not an app issue but an OS issue. OEM ROMs close background apps very quickly to improve battery life. This is especially a problem on Xiaomi phones. It just looks like it crashes when you try to open it. It actually closes earlier and you may see a screenshot of its last state.

    • Darkassassin07@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      No. Battery optimization is disabled for this app, it’s far more abrupt than a power managed app, and there are crash logs.