Application crash when re-indexing an MD graph for the second time

[lhewett946]

Search first

• I searched and no similar issues were found

What Happened?

Following on from #265, I tried reindexing for a second time to see if that improved the situation further and was instead confronted with the following:

Full text of the notification is:
Error caught by UI! Error: No protocol method IDeref.-deref defined for type null: Error: No protocol method IDeref.-deref defined for type null: at $APP.$cljs$core$missing_protocol$$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/shared.js:2882:10) at $APP.$cljs$core$_deref$$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/shared.js:3231:20) at $APP.$rum$core$react$$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:12581:15) at $frontend$util$react$$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:15707:77) at $frontend$components$journal$sub_journals$$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:76754:72) at Function.<anonymous> (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:155262:28) at $APP.$cljs$core$apply$$.$cljs$core$IFn$_invoke$arity$2$ (file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/shared.js:37731:180) at file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:12518:135 at file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:89012:503 at file:///C:/Users/louis/AppData/Local/Logseq/app-0.11.0/resources/app/js/main.js:96116:168

Reproduce the Bug

1. Download the attached graph, unpack and open in Logseq
2. Reindex
3. See that not all visual glitches are fixed
4. Reindex again and the app should crash

Expected Behavior

The app should not crash

Files

Logseq-New.zip

Browser, Desktop or Mobile Platform Information

Windows 11
Logseq Windows build (signed) downloaded from https://github.com/litcu/logseq/actions/runs/14767333490 - current revision shows e4389bb-dirty

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]

@lhewett946 Hi. Thanks for reporting. A fix has been pushed