Dragging cards in collections' Kanban view causes 200+% CPU usage of anytypeHelper in a vault with 400+ objects

[hatbox4887]

WHAT IS THE BUG

After dragging the card of any object (e.g. a Page) in the collections’ Kanban view from one column to another, the CPU usage of anytypeHelper process becomes 200+%.

High CPU usage lasts 30 minutes minimum, and it causes the laptop surface to become hot and drains battery faster. I do not have information if it may drop after some idle time.

After quitting AnyType and launching it again, the CPU usage of anytypeHelper is normal.
The data is in the expected state (the card belongs to the column where I dropped it).

While restarting resolves the problem of high CPU usage, it does not make usage of AnyType comfortable at all.

HOW TO REPRODUCE IT

1. Open the local-only vault with 400+ Pages that are linked to a single collection

2. Open the Kanban view of this collection with grouping by the Tag property of the page

3. Drag some card in some column and drop it in another column

4. Open Activity Monitor

5. Notice that CPU usage of anytypeHelper is increased (200+%) and does not drop

   

6. Quit AnyType fully

7. Launch AnyType app

8. Notice that CPU usage of anytypeHelper is normal and data is in the expected state.

THE EXPECTED BEHAVIOR

The CPU usage of anytypeHelper does not significantly increase right after drag-and-drop in Kanban view.

ADDITIONAL CONTEXT

• Vault is in local-only mode

• Vault contains 400+ Pages

• Kanban contains 6+ columns

• Page is a default type (it is not modified except the Tag property — new options are added)

I have tested this behavior on a clean empty space by creating 400 empty Page objects in Kanban view.
After completing reproduction steps, the CPU usage increases up to 100% (luckily not 298% as in the previous screenshot).
But the behavior is the same: high CPU usage lasts long — restarting the app somehow fixes high CPU usage.

I would appreciate any information that could help to prevent this kind of anytypeHelper behavior without constantly restarting the app.

TECHNICAL INFORMATION

OS version: darwin arm64 15.7.4
App version: 0.55.4
Build number: build on 2026-05-04 16:31:34 +0000 UTC at #545ed723e3e227b1f0906ec57aaf4adea24d06ec
Library version: v0.50.4
Anytype Identity: AArLRHjZDX6VkhEqkDJPGZizbAgt7HxQh6Z3db9Y8igvuo3v
Analytics ID: MdC9rrV5v111tEqZYzkn8tvrUpoJTMdaaey8oyFFvdt2B4Fb
Device ID: 12D3KooWS8q2G85YMKttNV2FkB74DqrZJ5NCYVt9vnAvcgD2uLRA
Ethereum Address: 0x25E218823baeEa87B4E8e8aA0170D19E12d67b26

[mariusgerome]

I also experience some unusual lag at some points (also while dragging and rearranging things), maybe this has to do with actual performance instead of just being an ui bugg… hmm

[hatbox4887]

Maybe. In this particular case, it is not just a temporary lag; it is just continuous spiked-up CPU usage (at this moment unreasonable).
I thought that it was occurring due to the specifics of the local-only mode (e.g., saving changes locally, and it takes so much CPU due to the vault data amount, idk).

However, it is very strange that it lasts at least 30 minutes continuously and may be fixed right away just by restarting the app.
So it looks like it should not really happen at all…