Logseq freezing even do anything

Questions & Help
1

I search all the case of freezing and me not like that.
THE CASE
Each time I restart my Macbook, it works well, I can click to anywhere and edit the block easily.
But after using a sort of time:

  • If the frequency of clicking to edit the block is low, for example about 4-5 minutes for each. It will be freezed after about 30 minutes.
  • If the frequency of clicking to edit the block is high, for example half of minutes to about 10 seconds (because sometime I have to edit the query or something like that) I will be freezed after about 3 minutes.

SOLUTIONS I DID AND NOT WORK
I did all the solution to fix this but hard, the only way to fix it temporarry is restart the laptop. Including:

  • Only use logseq alone. Yes, no more other app is running beside it.
  • Make more storage for my computure, yes. I have more than 200 GB free disk.
  • Clone the folder. The fact, other graph with less pages still freezed. I think it is not about the size of the graph.
  • Disable all plugins when it is freezed. It was still freezed.
  • Clear cache. Even the the demo docs after clearing cache also being freezed. And I open my graph, it is still freezed.
  • Re-install Logseq.

THE ONLY SOLUTION
Is restart my computer then use it. But, sometimes when working, there are a lot of things that I have to solve, so I cannot restart.
At that time, I have to go the page of that block then click to create a new block, then use the up arrow to edit that block. But some of these days, It even freezed and cannot create a new block by that way.

SOLUTION DID’NT TEST

  • Running logseq with single plugin till it is freezed. This is crazy and I really don’t want it. But seem that I have to test it.

QUESTION
Do you guys meet and have any solution for this?
Please just give me ideas is ok.

2

First I would have a look on the process list.
I’m more the linux guy who would use top or htop on the terminal. But also “Activity Monitor” should work to give you an overview what is happening on your system while the problem occours.

  • are there any processes with high cpu or memory usage while the issue occurs
  • what is the load on the logseq processes during the issue
  • how much memory is left free in the system etc.

Next would be to have a look on IO ussage on the hard disks etc.
Are the files of your graph on disk or Icloud-Share Folder etc?
Are there any processes hanging while writing to the disk etc.

Just a guess. But I would start with this

Could also be a plugin.
But in this case I would deactivate all plugins first and see if there is no issue at all.
If there is no issue at all without a single plugin - you know where to dig deeper.

1 Like
3

About the overload, you can check my list, there are 2 options that I tested but still not work:

  • Only work with logseq and it don’t have any lag or high CPU of-course. I’m using Macpro M1.
  • There are more than 200 GB memory left in the system.
    About the plugin, I also did it: disable all the plugins when it was freezed but still cannot help.
    It might be plugin confliction, and I’m testing one by one. But this really really take time.
4

Ah, yes - overlooked that statement in your list.
Also the size of the graph should not be the issue as you wrote.
that’s somehow strange…

1 Like
5

Just using logseq since 3 weeks again.
On Linux with ~200 pages
And on Mac Mini M2 16GB ~ 2000 pages
Had some issues related to memory on Linux, but so far it seems to be that it only had been a temporaly issue with system load during tha single moment.
So I am debugging further on my setup. Had no issues so far on macOS , also the graph is bigger there…

6

I have the same number of pages as you (204 pages). But the content is not much in each single page.
The fact, even some time the system is lagging because there are to many app, the logseq is still working well.
So, I think even not relate to the system loading much. The problem is somewhere in some plugin I think.
Just share here if anyone met it can help me faster.

7

It because the plugin confliction.
So, just find the plugin that cause then disable.
The method is that disable all plugin first → then restart the computer → then use the logseq to check one by one till firgure which plugin cause the problem → then remove it.
Cannot wait till it freezed then disable all plugin then enable one by one at that time to check. Because as I mentioned above when it’s freezed whether disable all or not it still freezed.

2 Likes