Logseq refresh for any longer page

I know this topic has posted on several platforms and this might be a double. But this is really pissing me of as this seems to be an issue across platforms and operating systems.

I have all my work documentation in my graph and any page that is longer then lets say only 50+ blocks is auto refreshing the page every 2 seconds making it un usable.

I really need a fix for this or I have to migrate all my data into another software.

Welcome to Logseq and the community @Unbroke2088!

Where have you stored your graph on disk? Because what you describe tends to happen when you save a graph in iCloud, Dropbox, Google Drive, etc. These services often sync selectively, or they might overwrite changes you make in Logseq. All in all, Logseq and third-party sync services (apart from Git) just don’t play nicely. That’s why we’ve created Logseq Sync (still in beta, but much more stable than for example iCloud. You can DM me for a free extended trial).

If this isn’t it, please share some more context about your setup like the devices you use, what OSes, what version of Logseq you’re on, what plugins or theme you use, anything else that could be special about where you’ve stored your graph (a network drive, an encrypted drive, a drive managed by your IT department). The more context you can give, the easier it’s for us to help you.

Hi, it is stored on onedrive. If this is the issue I will try storing it on the hard drive and checking if the issue persists. Thanks for coming back so quickly on this will let you know.

Issue remains.

I have a page that has 238 blocks, when I scroll down the page to around the 50th or 60th block the page auto updates every 2 seconds making the page unreadable. I can only make this less frequent when I collapse all the blocks and open them one after one. But this is just not practical for some pages.

The OS is WIN11
Logseq version is 0.10.9
Synch (Logseq Synch) is enabled
Pluggins Active are Bullet Threading / Journals calendar and Todo List

There seems to be a slight workaround but this is simply not practical:
I can nest all the information into sub pages but then another issue happens in that the linked references on the page auto update every 2 seconds.

On another thread with the same issue I found that some suspect this to happen because of a file handler routine that triggers a refresh upon scroll.

Using OneDrive and Logseq Sync in combination is recipe for performance issues and potential data loss. That’s why there’s this big warning in the Logseq Sync onboarding guide:

How have you moved your graph? Hopefully you’ve followed these instructions and safely unlinked it, moved it, and then relinked:

1. Unlink your graph

In the top of the left sidebar, click your graph name and then the All Graphs button.

On the All Graphs page you’ll see all of your graphs. Click the Unlink button after your graph that you wish to sync using Logseq Sync.
Keep this All Graphs page open for the third step.

2. Move your graph folder

Using File Explorer (Windows) or Finder (Mac), move the folder containing your graph out of any synced folder, onto your local device only.

If you’re using Logseq on iOS, make sure that your store the graph in the Logseq folder on your iPhone or iPad. If you store the graph outside of the Logseq folder, you won’t be able to use Sync. Don’t see the local Logseq folder? Restarting your iOS device will solve the issue.

3. Link your graph

On the All Graphs page, click the button that says Open a local directory and select the local folder that contains your graph. You’re now ready to follow the rest of this guide.

If you’ve done this, make sure you also do a re-index (in the left sidebar, click your graph name in the top and then re-index).

If you still have performance issues after all of this, can you share a bit about the hardware? For example, are you using an Arm processor (and therefore Windows 11 for Arm), is your local folder stored on a network drive in any way, is the drive managed by your work IT, is it an encrypted drive? These could all have an impact, so please share as much as you can about your setup.

Hi,

yes I have done this exactly this way. The issue remains.

The pc is a lenovo thinkpad x1 carbon 12.
Processor is the Intel Core Ultra 9

But I can tell you already that this is not hardware related as I have the same issue on my private PC, local graph storage same Logseq Version. And I also had it on my previous work PC (Dell Latitude, Intel Core 7) with local graph storage.

For me this behaviour startet from one of the 0.10.x versions not sure which one of those it was exactly.

Is there a way to get older logseq versions to just test if this is version related?

28.10.2024_15.36.04_REC-ezgif.com-video-to-webp-converter
You can see the behaviour in this animation.

One last bid of information as I have also tested this. This is only on pages. If I put the same blocks into a journal page this behaviour does not happen. And even more strange is when I have this block set doubled in a journal page the behavior on the page also stops.
But the solution for me cannot be that I put all my longer page sets into journal pages.
So this has to be an issue with logseq page update processes.

Thank you for the extra context. I’ve had a similar issue happen when referencing blocks, and the Linked References behaving similarly. But that’s because whenever you reference a block, the Markdown file containing that blocks gets updated.

In other words: it seems like somehow the page gets updated (constantly). That’s why I recommended a re-index, but if you’ve done that and the issue persists then there might be something else going on.

Maybe another app that tries to backup or otherwise access the pages folder? Maybe it’s an access rights issue? Maybe there’s accidentally another graph nested in the pages folder? It could be many things, unfortunately.

If you want us to further investigate, can you please send a console log to support@logseq.com? That will help to diagnose the issue.

Here are instructions on how to export console logs (it’s written by Figma but in Logseq it works the same):

You can find all releases in our GitHub repo: Releases · logseq/logseq · GitHub