big bugs lead to crashes, inability to edit typing, inability to input data, and many tags property are garbled！！！

[babygaogao]

Search first

• I searched and no similar issues were found

What Happened?

The database that is currently in existence and operating daily has stagnated. Although data has not been lost temporarily, a large number of tag property have become garbled and frozen, making it impossible to continue inputting or editing any logs or journal. The notes are in a state of stagnation.

1. Unable to edit typing, unable to input anything, daily logs cannot be edited or input properly.

2.Clicking to enter the tag page, you will find that most of the property values are garbled.

3.After refreshing the page, it shows an error.

Reproduce the Bug

1. Click on any log, such as the log from the most recent day

2. Edit and type, but can only input one line; pressing enter is ineffective, and cannot continue typing.

3. Click on any tag

4. Edit in the properties bar

5. Report a bug

6. Click any database button on the tag page, such as list or sort, then click any item in the dropdown popup

7. Crash

Expected Behavior

No response

Files

No response

Browser, Desktop or Mobile Platform Information

Logseq database version
Microsoft Edge
win11

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!)

[logseq-cldwalker]

Hi. Sorry to hear. Could you export your graph as a debug transit file as described in https://github.com/logseq/docs/blob/feat/db/db-version.md#export-and-import and share it? If not, are you able to run commands from Command-shift+P on mac/linux or Ctrl-shift+P on windows?

[babygaogao]

Hi. Sorry to hear. Could you export your graph as a debug transit file as described in https://github.com/logseq/docs/blob/feat/db/db-version.md#export-and-import and share it? If not, are you able to run commands from Command-shift+P on mac/linux or Ctrl-shift+P on windows?

Hello, I think this really isn't my problem because I used to back up every day, and those backup files themselves are fine. I tried to import the previous backup files and found that each one had the same issue #213 #213 . In the past few days, other people have reported similar errors, and I believe this is a problem with an update on your system. Of course, creating a new database has no issues. The problem is that the database we have been used to for the past few months has suddenly been locked and cannot be edited. If this happened with data that was currently being processed, it wouldn't matter; I would just clear everything, delete it,Clear all cache, clear browser cache, and import the backup database from a few days ago . However, when importing, the issue #213 #213 also occurred, and the imported database is also locked and cannot be edited.
these past backup databases have been verified to be fine, last month, when I cleared my browser cache and all data was wiped, I re-imported the database using this backup file, and there were no issues at all. Therefore, the past backup database files are usable. I have gone through several rounds of browser cleaning, each time to speed up performance by clearing the cache, so I have imported and exported such backup files several times, and they have all worked very well. Therefore, given that I back up almost every week, I cannot understand why this time the data import error is locked and cannot be edited, as these are not emergency backup files created after a crash, but rather backup files that have been verified multiple times to import and export perfectly.
This issue started at least on January 24, 2025, possibly due to an update at that time.Having experienced the issue of the database being locked, I reflected on the data backup problem of Logseq. Of course, there was no data loss; the data is intact. However, it was locked and could not be edited. If other users encounter this situation in the future, how many people will have the patience to create a new database and copy and paste the data day by day? While the data is not lost, the database being locked and the logs being locked and uneditable will lead to stagnation. Logseq should address this issue.

[babygaogao]

Hi. Sorry to hear. Could you export your graph as a debug transit file as described in https://github.com/logseq/docs/blob/feat/db/db-version.md#export-and-import and share it? If not, are you able to run commands from Command-shift+P on mac/linux or Ctrl-shift+P on windows?

Hello, I think this really isn't my problem because I used to back up every day, and those backup files themselves are fine. I tried to import the previous backup files and found that each one had the same issue #213 . In the past few days, other people #213 have reported similar errors , and I believe this is a problem with an update on your system. Of course, creating a new database has no issues. The problem is that the database we have been used to for the past few months has suddenly been locked and cannot be edited. If this happened with data that was currently being processed, it wouldn't matter; I would just clear everything, delete it,Clear all cache, clear browser cache, and import the backup database from a few days ago . However, when importing, the issue #213 #213 also occurred, and the imported database is also locked and cannot be edited. these past backup databases have been verified to be fine, last month, when I cleared my browser cache and all data was wiped, I re-imported the database using this backup file, and there were no issues at all. Therefore, the past backup database files are usable. I have gone through several rounds of browser cleaning, each time to speed up performance by clearing the cache, so I have imported and exported such backup files several times, and they have all worked very well. Therefore, given that I back up almost every week, I cannot understand why this time the data import error is locked and cannot be edited, as these are not emergency backup files created after a crash, but rather backup files that have been verified multiple times to import and export perfectly. This issue started at least on January 24, 2025, possibly due to an update at that time.Having experienced the issue of the database being locked, I reflected on the data backup problem of Logseq. Of course, there was no data loss; the data is intact. However, it was locked and could not be edited. If other users encounter this situation in the future, how many people will have the patience to create a new database and copy and paste the data day by day? While the data is not lost, the database being locked and the logs being locked and uneditable will lead to stagnation. Logseq should address this issue.

[tiensonqin]

@babygaogao It's definitely not your problem, it'll help us debug and fix this issue if you can provide us with a debug transit file as mentioned here.