I can't exit logseq without having to force-quit. Overall macOS system slowdown

Feedback Bug Reports
1

My setup: I am running a large logseq database using the Readwise plug-in. Around 19000 pages. Running on an M1 Mac mini and 16 GB of RAM. All files are sitting outside of my iCloud folder.

It might be a difficult one to pin down, but in effect I’m experiencing an overall slowdown of my macOS system when logseq is running (closing all other apps except for Safari). If I quit logseq or restart the computer the problem fixes itself.

Then, I find myself having to force quit or cancel the process from the Activity Monitor. CPU and memory usage remains fairly under control, with no big spikes.

What actions can I take to start debugging the issue? Perhaps the Readwise plugin has something to do with it?

I tried re-indexing the database doesn’t do much of a difference.

2

Do you use logseq sync by chance?

3

Can you record a performance profile?

4

No logseq sync. However, on that directory I am running a git repo to publish my changes.

That could be part of the issue.

5

Yes,

Here you go:
https://drive.google.com/file/d/1Juy8Lkm7TO6otHg7QBzopGR-Ry48Nglj/view?usp=share_link

1 Like
6

Given the exception event captured:

image
image1116×576 68 KB

Any console output captured when you exit the program?

Seems to be the case of Unable to close Logseq · Issue #8536 · logseq/logseq · GitHub
But we have no deterministic way to reproduce the issue.
Do you have any clue to reproduce it?
Is this issue happening on a new graph?

7

Is this working for you?

I did have git auto commit enabled, it is now disabled and appears to be working.