Our favourite anytypehelper high CPU (and RAM) usage is back again. The helper uses around 4–6 GBs of RAM and 100 % CPU constantly. It is caused by being the in Local-First Lovers shared space. When leaving the shared space, the issue disappears (after a restart of the application).
How To Reproduce It
Join Local-First Lovers shared space.
Enjoy the free room-heating feature of Anytype.
The Expected Behavior
Normal workload.
Additional Context
Furthermore, while testing this issue, I managed to somehow break my vault. I do not see the Local-First Lovers space any more after leaving the space, but when I try to join the space again, it says that I already joined the space. And the anytypehelper CPU usage goes up, a sure sign of being in the Local-First Lovers space. The problem is that now I cannot leave the space as I already left the space and the space is not visible in the UI anywhere. Clicking the button to open the space when clicking the join link does not do anything (does not open the assumedly already joined space). I was able to un-break the vault by reverting to 0.43.1 where I can see the joined space, leave the space and return to 0.43.4.
Device
Lenovo ThinkPad T14 Gen 4 Ryzen
OS
NixOS unstable
Anytype Version
0.43.4
Network Mode
AnySync
Technical Information
OS version: linux x64 6.11.5
App version: 0.43.4
Build number: build on 2024-10-31 14:14:45 +0000 UTC at #5ede1352da2eb6be9c64ee3b29c22e9cdb9e4b6d (dirty)
Library version: v0.36.7
Anytype Identity: < redacted >
Analytics ID: < redacted >
Device ID: < redacted >
Came here to report the same bug. Using Anytype 0.43.4 on MacOS 15.0.1. Facing this issue since the last two updates. Anytype has become unusable on my mac. Please resolve this soon.
UPDATE:
I am not facing the high memory and CPU usage issue after I left the “Local-first Lovers Club” shared space that was created by AnyType team. Same on android as well. It is working fine.
Maybe there is some issue with handling huge spaces or there might be some issue specifically in the “Local-first Lovers Club” space.
@Adda are you part of the “Local-first Lovers Club” space as well? If so, you can try to leave that space and see if it makes any difference.
I experienced this shortly after updating to version 0.43.4 as well (anytypehelper was using up to 300% CPU), but strangely enough the issue resolved itself after a few minutes and the CPU usage went back to a normal, low value. Currently I don’t see any problem with high CPU usage on macOS anymore.
When I had issues with the anytypehelper in the past regarding the shared space Local-First Lovers, the issue resolved itself once, too, but other times the issue persisted. Now, even after a few hours of running, the anytypehelper keeps using 100 % CPU a GBs of RAM.
I noticed the same issue on my android phone as well. After opening and using anytype for a couple of minutes, my phone became very sluggish and lagging. And the ram was almost fully used up.
Yeah, I had to leave the Local-First space too, and the problem seems to have disappeared on both of my iOS devices. On the other hand, everything was fine on the desktop.
Btw, maybe it was due to the new chat object in the space that didn’t have support on the mobile versions of the app? As a guess…