Logseq 0.7.2 unresponsive and high memory consumption

[konsumschaf]

What happened?

Windows: After updating from 0.7.1 to 0.7.2 logseq is unresponsive and consumes a high amount of memory (~2000MB in Windows) ~300MB for 0.7.1

Linux: After updating from 0.7.1 to 0.7.2 logseq is unresponsive and consumes a high amount of memory
When started from the terminal, I get lots of errors flying by

(node:28223) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1582)

as well as warnings about too many open files.

Reproduce the Bug

1. Update from 0.7.1 to 0.7.2
2. Restart App
3. Enjoy

Expected Behavior

Same performance as with 0.7.1 and no crashes

Screenshots

No response

Desktop Platform Information

Windows 10, 0.7.1 -> 0.7.2
Linux (Ubuntu 21.10) 0.7.1 - 0.7.2

Mobile Platform Information

No response

Additional Context

No response

[CharlesChiuGit]

0.7.2 freeze and not response on Win11 21H2 22000.708.
0.7.2 works fine on my Win10 21H2 19044.1741 laptop, using the exact graph and plugins like in win11. No high cpu usage on my end, but this weird error.

[abdgad]

The same thing happens on Windows 10. It's not responsive.

[andelf]

Could you try the nightly release? https://github.com/logseq/logseq/releases/tag/nightly

[CharlesChiuGit]

Seems like the nightly release fixed both win10 and win11's problem for me and it works pretty well!

[andelf]

@CharlesChiuGit Thanks. We will cut a new release soon.

[konsumschaf]

Could you try the nightly release? https://github.com/logseq/logseq/releases/tag/nightly

Just did a quick test, everything works again, thanks a lot for the quick fix! 🙏

[dodyg]

Yup, the nightly build works now again on Windows 11.

[konsumschaf]

Tested for Linux as well, closing this as the fix works (and we have a working 0.7.3 now ;-) )