logseq / logseq/db-test

Cant open old large graph

Open
#910 6 comments 0 reactions 1 assignee View on GitHub

@tiensonqin is already working on this.

Since Jun 2, 2026.

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

Description

Search first
  • I searched and no similar issues were found
What Happened?

Since like 3 weeks ago, when I opened Logseq the app would sometimes not recognize any graphs and it would show no graphs. However this would be fixed after closing and opening the app again
Today however, it wasnt fixed. I then created a new graph and I was able to write on it. Then all my other graphs showed up. However the app still cant open my main graph which I have been using for months now (logicalSeqPo on the video), it just hangs and no errors show up on the console

Reproduce the Bug
  1. Open the app
  2. Try to open my main graph
Expected Behavior

No response

Screenshots

https://github.com/user-attachments/assets/6833da12-df8f-4e2f-b27e-09df8fd494d1

Files

No response

Browser, Desktop or Mobile Platform Information

No response

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)

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.