App crashes quite frequently

[xingped]

At least once a day the app completely crashes and closes out when opening the comments on a post. This has been happening for a while now, at least a month.

I'm not sure how to give more info than that, but if there's some way to provide logs or other necessary information, let me know.

[Livinglist]

Hi @xingped , can you send me the logs next time you encounter the crash? Also what's the spec of your device? I'm curious about the platform (android/iOS), the RAM and the storage capacity.

You can download the logs by:

1. go to settings in the app.
2. scroll to the very bottom.
3. long press on the About button/tile to enable the dev mode.
4. taps on Logs button/tile, and download it.
5. long press on the About button/tile again to exit the dev mode.

Thank you.

[eames-palmer]

I can replicate this by opening a handful of articles in a row and expanding comments (I have "Default fetch mode" set to "Lazy").

Unfortunately, the log window remains blank on my current installed version. It might be due to the debug .apk, but that would be counterintuitive. I wasn't able to find a stack trace in the system logs either (if those are even expected to surface correctly there).

Currently on a Pixel 9 Pro running Android 17.

I will see if I can replicate it again once the newer release drops, and/or when I get a chance to uninstall/reinstall.

Side Note: Pressing the debug tile multiple times appears to create multiple nested intents on android. Meaning you need to go back for each one to get back to the previous page.

[eames-palmer]

I am seeing logs for a default v3.6.7 install from F-Droid, but none are related to the crash. No stack traces or exceptions.

[xingped]

A precursory scan of the logs after crash doesn't cause anything to stand out to me, but logs file attached.

Phone is on Android 16, 12GB of RAM, and 512GB of storage.

hacki-logs.txt

[eames-palmer]

Seems like it is probably an OOM bug based on the behavior. If there isn't already native logging set up, that might help?

Regardless, there is probably some memory leak, and/or the app isn't cleaning up article/thread resources as it is running.