• Rubén@lemmy.worldMEnglish
    16·
    10 months ago

    The images are too big to be loaded inline. I’ll find a fix. Thanks for the link

  • fixmycode@feddit.clEnglish
    3·
    10 months ago

    welp, did it for me too, Samsung S23+, Android 14, 1.0.4.

    Although I believe it’s not reporting as a crash, the app just closes, you can see the activity still running on the app switcher, but selecting it doesn’t return you too the thread, it takes you to the homepage. Seems to be related to the number of inline images on the thread (so far just 6, but they’re very HD, the thread is about a guy testing his new camera on his cat)

    • Martin@feddit.nuEnglish
      2·
      10 months ago

      This is usually what happens when the app runs out of memory. The process is just killed

  • topher@lemm.eeEnglish
    2·
    10 months ago

    Can confirm, it crashed for me too. But not until a second or two.

  • FireWire400@lemmy.worldEnglish
    2·
    10 months ago

    Does for me too, almost instantly at that. Pixel 6 Pro, Android 14, Boost 1.0.4 (7).

    Might have something to do with the size of the pictures, Boost tends to lag heavily when there’s big pictures, at least for me.

  • lixus98@sopuli.xyzEnglish
    2·
    10 months ago

    Didn’t crash for me LineageOS 20 (Android 13). Boost 1.0.4. Moto g52

    Edit: it did eventually crash :(

  • Beans@sh.itjust.worksEnglish
    2·
    10 months ago

    Crashed for me, seemingly as it was loading the top image as the second image loaded in fine. (LG G8 (not G8X, etc.), Android 11, Boost 1.0.4)

  • Gerudo@lemm.eeEnglish
    1·
    10 months ago

    Same here. Just kicks me to my home screen. Samsung 20 FE. Android 13