app crashes after loading graph

[zipproth]

Search first

• I searched and no similar issues were found

What Happened?

After updating the app from version 0.9.15 to 0.9.18 on my Android device, the app consistently crashes after a few seconds. Following the crash, Android displays a dialog indicating that the app has been crashing repeatedly. Uninstalling and then reinstalling version 0.9.18 - which forces a graph re-indexing - fails to resolve the issue. Note that no crash happens during re-indexing (which takes several minutes in my case).

An attempt to downgrade to 0.9.17 yielded no improvement. I was unable to find an APK for version 0.9.16 for further testing. Reverting back to 0.9.15 resolved the issue and restored functionality.

Version 0.9.17 runs smoothly on my Linux machine with the same graph. Additionally, both 0.9.17 and 0.9.18 on Android are able to load a different, less complex graph without any issues.

Reproduce the Bug

Upgrade to version 0.9.17 or 0.9.18 on Android, using a graph containing approximately 9,000 files and 2.4 GB of assets, along with complex queries. Note that this is based on my personal experience; the bug does not occur when loading a smaller graph with fewer queries.

Expected Behavior

The expectation after an update is to be able to successfully load the same graph as before. If there were any size restrictions introduced in versions after 0.9.15, an appropriate error message should be displayed rather than experiencing an app crash.

Screenshots

Desktop or Mobile Platform Information

Android 13, T1TR33.43-20-48 (August 1 2023)
Moto Edge 40 Pro

Additional Context

What would be the best way to generate a log that could assist in debugging this issue?

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[andelf]

using a graph containing approximately 9,000 files and 2.4 GB of assets

I haven't used Logseq on this scale of repo. I need more investigation.

[zipproth]

Thank you for your prompt response. I appreciate your willingness to investigate this issue further. I would like to clarify a few points:

• Stability Until Version 0.9.15: The graph has been stable and functional up to version 0.9.15 on my Android device. Hence, I'm inclined to think that the issue was introduced in versions 0.9.16 or 0.9.17, rather than being a consequence of my graph's size.

• Labeling as 'Performance': I noticed that this issue is labeled as a 'performance' problem. While the term may be appropriate in some contexts, I feel that in this case, the primary concern is the app's crash, not its performance.

• Constant Graph Size: It's important to note that my graph size didn't suddenly inflate; it has been gradually growing slowly. The total file size of my *.md files is just 12.8 MB - the mentioned 2.4 GB are mainly assets. The number of *.md files is currently 5434.

Would it be helpful for you if I provided any additional information? Meanwhile, I'm confined to using version 0.9.15 on my Android device until a resolution is found.

[alercah]

I am experiencing this issue as well with version 0.9.20.

It is not graph-specific; it happens even if I unlink all graphs and sit on the welcome acreen.

Clearing all local data of the app helps for a short while.

[zipproth]

Recently, I attempted to upgrade my Logseq Android app to version 0.10.3, but unfortunately, the problem persists. Currently, I am constrained to using version 0.9.15, as later versions do not function properly for me. This issue is exclusive to the Android app; I have not encountered similar problems with the desktop version, despite using the same graph.

In my journal, I utilize a substantial number of queries, particularly for categorizing to-dos. In an effort to provide more detailed diagnostic information, I plan to replicate my graph and temporarily remove these queries to ascertain if they are contributing to the issue.

It is important to note that this crashing issue did not occur in any of the previous versions up to 0.9.15, even though I used the same queries and the graph was comparably large.

[alercah]

I have not yet tried downgrading, but 0.10.5 still has the issue.

After clearing local storage, the app works for some amount of time that is more than 30 minutes and less than 24 hours, before beginning the crash cycle again. Clearing local cache is not enough.

[andelf]

Thanks for your report. I still can't reproduce this on all my test devices.
The changes introduced in 0.9.16 are at 0.9.15...0.9.16 .

It would be helpful if you could provide any error logs via adb logcat.

[alercah]

Is there a way to get logs on a phone that isn't in developer mode?

[andelf]

Thanks. I can add some error reporting to the nightly release.

[andelf]

Could you try the nightly release?
https://github.com/logseq/logseq/releases/tag/nightly

[alercah]

Sure. I have used it and crashed it; how do I get the logs to you?