logseq / logseq/db-test

App crashes or becomes unusable when opening a specific DB graph on the latest nightly

Open
#1,136 0 comments 0 reactions 1 assignee View on GitHub

@tiensonqin is already working on this.

Since Sep 1, 2026.

bug
Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Search first
  • I searched for similar issues
What Happened?

The latest Logseq nightly crashes or enters an unrecoverable error state when opening one specific DB graph.

The app initially appears to load, but shortly afterward the UI becomes completely unresponsive. On Desktop it shows the “Something went wrong” recovery screen; on Android, none of the buttons can be pressed.

This occurs on both Android and Desktop nightlies.

The same graph works on the 20260728 nightly. A test sync-smoke-test graph works on the latest nightly.

This reproduces with the graph theme removed: both custom.css and custom.js are empty.

Reproduce the Bug
  1. Open the affected DB graph on the latest Android nightly.
  2. Let the Journals view load.
  3. The journal flashes/rendering appears briefly, then the UI stops responding and buttons cannot be pressed.
Expected Behavior

The graph should open normally and the application should remain usable.

Comparison
  • The same graph works correctly on the 20260728 nightly.
  • The sync-smoke-test graph works correctly on the latest nightly.
  • The issue occurs with the theme removed.
  • custom.css and custom.js are empty.
  • This therefore does not appear to be caused by the theme or custom JavaScript.
Platform Information
  • Desktop: latest Logseq nightly, Apple Silicon macOS
  • Android: latest Logseq nightly
  • Exact device, OS, and build numbers: [add details here]
Additional Context

The failure is graph-specific and reproducible across both Desktop and Android latest nightlies. A sanitized debug Transit export is attached to help reproduce the issue.

Files

logseq_db_Abhilesh_Knowledge_Graph-debug-datoms_1788248450.transit.zip

Additional Context

The desktop recovery screen only offers SQLite export. The debug Transit export was obtained from the working 20260728 desktop client so the graph data can be reproduced without sharing the raw SQLite database.

Are you willing to submit a PR? If you know how to fix it.
  • I'm willing to submit a PR

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.