hyperion-project/hyperion.ng

[WARNING] macOS Sequoia exposes(?) extreme memory leak

Rastafabisch opened this issue · 5 comments

Rastafabisch commented
  • I confirm that this is an issue rather than a question.

Bug report

I just realised, that Hyperion cannot be used on macOS Sequoia (beta 1, Apple Silicon).
After updating my Mac to the current beta Hyperion causes the WindowServer UI management process to consume immense amounts of RAM (as in GBs/s) which crashes the system unrecoverable. No other screen-grabbing application I tested so far exposes this behaviour.

I tested several arm64 as well as Intel builds (via Rosetta) on my MacBook Pro 16" (M1 Pro).

I will continue to observe this behaviour and update this post accordingly. The current ticket number within the Apple Feedback system is FB13910081.

hyperion-project commented

Hello @Rastafabisch

We make use of an ISSUE TEMPLATE to capture relevant information to support you best. Unfortunately, you ignored or deleted the given sections. Please take care that all information requested is provided.

This issue will be automatically closed by our bot, please do not take it personally. We would like asking you to open a new issue following the ISSUE TEMPLATE.

Thanks for your continuous support!

Best regards,
Hyperion-Project

Lord-Grey commented

@Rastafabisch Thanks for sharing your finding.
Would be good, if could keep us posted!

  • 👍1
Rastafabisch commented

The issue is still and unchanged (possibly worse?) in Beta 2.

Within seconds WindowServer consumes more than 60GB of RAM.

Rastafabisch commented

Apparently Beta 2 also evokes another issue, I did not realise previously. Hyperion itself now always consumes around 90% macOS CPU cycles (100%=One Core). Also it now often freezes, especially after system sleep. I did not experience this on Beta 1.

Due to the main issue (windowserver) I currently use Hyperion without screen grabbing access, which on macOS to not cause any unknown behaviour basically only allows access to the desktop background, but not any content or applications.

Rastafabisch commented

The WindowServer memory issue triggered by Hyperion seems to be resolved with beta 3.

Hyperion still appears to be using abnormal amounts of CPU. Using the QT grabber an entire core is used. With the OSX grabber around 20-30% of one Core on my MacBook Pro with M1 Pro chip are used. That is still 50% more than it used to be under Sonoma, if I recall correctly. I also credit the occasional flickers to black to this elevated processing needs, though that's just a hunch.