Andelf

Close as handled in help desk([email protected]).

@Enzo16ctcri Could you open the Developer Console and check if there are any error logs? Use cmd+shift+i to open the Developer Console.

Could you provide a screen shot of it?

This might be an issue in the main thread. Could you check `~/Library/Logs/logseq/main.log`? This should be resolved by "Clear Cache".

Thanks for the report. - On Windows, high CPU usage might be caused by Windows Defender - On other platforms, a performance recording with Developer tools will be helpful to...

@hmijail The screen shot of the result flamegraph is also helpful.(with zoomed view to the tallest and most time-consuming calling tree) Thanks for the detail. It seems to be an...

- Could you check the local date? - Are you behind any network firewalls? - Can you visit https://api.github.com in your web browser?

Sorry for the inconvenience. Introduced by https://github.com/logseq/logseq/pull/10884 > ubuntu18.04 GLIBC version is too old for the search index's underlying DB. You can use an older release for a temporary workaound.

Could you check out the latest Logseq log, located in `C:\Users\USER_NAME\AppData\Roaming\Logseq\logs\main.log`.

[email protected] is always available.