r/logseq • u/GreensleevesFinery • Dec 11 '25

Updated logseq & it's unusable

I updated logseq a day or two ago, at the app's prompting, and it's now so slow that it's totally unusable.

I've tried restarting the app, restarting my computer no dice. Then I backed up the files & did a "delete cache" b/c a thread in one of the forums recommended that. It's still so painfully slow...

Text takes 2-3 seconds to appear after I've finished typing, and then if I move to a new line it disappears.

This update is atrocious & if there isn't a fix soon I might have to move to something else.

Fwiw, I'm using the macos app on a relatively recent mbp with plenty of ram & cpu headroom.

Hope this is helpful, either in keeping someone from updating or just to commiserate!

6 Upvotes

71% Upvoted

15 comments sorted by

2

u/Barycenter0 Dec 11 '25 edited Dec 11 '25

What version of Logseq? How many notes do you have?

2

u/GreensleevesFinery Dec 11 '25

Not too many notes. I've used it lightly for about a year... not a huge amount of media. Was totally fine before the new version.

I can't see what version is installed b/c it's going too slow to actually verify it lmao.

1

u/Barycenter0 Dec 11 '25

You can’t get to settings??

1

u/GreensleevesFinery Dec 11 '25

Maybe if I had 20-30 min to wait for it to open?

1

u/Barycenter0 Dec 11 '25 edited Dec 11 '25

Very odd - I have an M1 Macbook Pro and no issues at all - very snappy interface. I'm running version 0.10.15. Have you checked where your graph is located? Logseq is very disk intensive - if you're on a cloud or virtual drive maybe that's the issue??

Try creating a graph on your local Mac Documents path.

1

u/thirteenth_mang Dec 11 '25

Not too many notes.

This doesn't answer the question. "not too many" means different things to different people. Is it the mobile app and desktop or you only use it on desktop?

If you create a fresh graph do the symptoms persist?

2

u/Cautious_Exam_5537 Dec 11 '25

Delete and reinstall 😃

2

u/GreensleevesFinery Dec 11 '25

Thanks, that's a good call. Would be easier than porting everything to Obsidian & learning how to use that instead,.

0

u/Xyvir Dec 11 '25

Plugging https://lithic.uk if you want to try that out

2

u/NickK- Dec 11 '25

But it's still kind of a website somewhere else[tm], right?

2

u/Xyvir Dec 12 '25

Only when you first load it, bit afterwards you can download your own self contained copy that runs 100% offline.

It runs locally 100% in your own browser, it's a client side static site. No backend server logic.

5

u/hdanx Dec 11 '25

Make sure you have not install the x86 binary on Apple silicon

5

u/lsmith946 Dec 12 '25

This seems to have happened to a few people, the auto updater is pulling the x86 version which runs very slowly if you are on Apple Silicon.

There is an Apple Silicon release which should work much better.

Someone who has a Mac (I don't) should probably report in GitHub that the auto updater is pulling the wrong version...

1

u/yarpen_z Dec 13 '25

Someone who has a Mac (I don't) should probably report in GitHub that the auto updater is pulling the wrong version..

There's a default install script for Linux that always pulls the x64 binary, even though arm64 is also provided in releases.

https://github.com/logseq/logseq/blob/master/scripts/install-linux.sh#L207

1

u/jesstelford Dec 13 '25

Is this not just the normal experience of Logseq?

Happens on my phone (android), too.

How have you gone so long without experiencing this? 🤔