Graph doesn't load

Nobody has claimed this yet.

### Search first

- [x] I searched and no similar issues were found

### What Happened?

When opening LogSeq a graph that I worked on the previous day doesn't load. When opening the "All graphs" page I get the "Something is wrong" page and a sidebar shows the following error:

```
Error caught by UI!
db-worker has not been initialized
Error: db-worker has not been initialized
at new $APP.sf (lsp://logseq.com/js/main.js:7823:31)
at $APP.Yg.C (lsp://logseq.com/js/main.js:13362:309)
at $APP.Yg.A (lsp://logseq.com/js/main.js:13362:263)
at cx.D (lsp://logseq.com/js/main.js:18952:87)
at aod (lsp://logseq.com/js/main.js:12527:260)
at lsp://logseq.com/js/main.js:12531:358
at lsp://logseq.com/js/main.js:8984:452
at gu (lsp://logseq.com/js/react-dom-client.production.min.js:2:96828)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113141)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113121)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
at es (lsp://logseq.com/js/react-dom-client.production.min.js:2:113186)
at Ju (lsp://logseq.com/js/react-dom-client.production.min.js:2:113025)
```

### Reproduce the Bug

I'm not sure what is causing it. Perhaps adding an image?! As it only started happening after I first used that feature.

### Expected Behavior

_No response_

### Screenshots

_No response_

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

Start by reproducing the failure when opening LogSeq and the "All graphs" page, focusing on the reported `db-worker has not been initialized` error. Trace the `db-worker` initialization path and the UI entry point represented by `main.js`; done means the graph loads and the error page no longer appears.

Written by the indexing model from the issue text.