Anytime Helper (Renderer) causes a lot of idle wake ups

Describe the bug
As can be seen in the screenshot below Anytype causes lots of idle wakeups (5-10x more than all other apps on my system, only topped by kernel_task). There is also a considerable amount of active threads.

It doesn’t matter whether the app is focused or not.

To Reproduce
Steps to reproduce the behavior:

  1. Open Anytype
  2. Observe Idle Wakeups in Activity Monitor

Expected behavior
Idle wakeups should be at a bare minimum to allow CPUs to return to idle.

System Information:

  • OS: macOS 12.3.1
  • Device Manufacturer/Model: MacBook Pro (16-inch, 2019)
  • Anytype Version: 0.25.4
1 Like

This is most likely the syncing in the background. But that’s just my assumption.
Does it have a negative impact on your system?

I’m not using Anytype anymore. However, idle wakeups usually mean that battery consumption goes up - the more wake-ups the more battery consumption as the CPU isn’t allowed to go/stay idle.

Not sure why Anytype would want to synchronize while the system is idle. Right after waking-up or next time the app is coming into foreground would be enough IMHO.

1 Like

I can confirm that Anytype Helper (Renderer) causes a lot of idle wake-ups on my Mac, second-only to kernel_task and close to other system processes.

However, I’m curious to whether this is actually a significant problem; I barely notice a negative impact to my system’s performance and battery life with Anytype active.

If your laptop is in sleep mode then it won’t actually sleep as Anytype will wake it up, I will try to find a solution on this.


@Razor Any updates on this? :blush:

I’ve found I cannot leave AnyType open on my Mac without it starting to seem to run the fan a LOT more than normal. This would explain it.

If Anytype is to become my go-to information repository - it is important that I’m able to leave it open! Indeed - would like to see a fix for this.

Does this still happen in latest versions?

@Razor I didn’t use AnyType anymore over the last few months due to this bug and settled with Logseq instead. So I unfortunately can’t really say how the situation is right now with the latest builds.