Screen Sharing overlay causes freezing of System Controlling (REPOST)

Question

Level 1

8 points

Screen Sharing overlay causes freezing of System Controlling (REPOST)

Hello, I'm reopening an issue perfectly described by another user which has been closed without any answer. This is very crippling and critical, and I could not find any solution.

When I try to share my screen with different applications (Discord, Google Chrome/Firefox, Safari, Telegram, etc), it causes a total freeze of Selecting Window overlay. I can't even click on any button on this overlay, I can't type anything in applications, some windows are blinking. The only thing working - touchpad gestures and maybe opening application by clicking on it in Dock, but I can't even click any element inside this application. I haven't found exactly the same problem online, but similar topics share solutions like `Disable Remote Management` doesn't solve the problem, because Remote Management is disabled in my system. Sometimes Screen Sharing works, but only if I do hard-reboot on this freeze. Also it may unfreeze in 1-10 minutes (can't detect how much long I need to wait until it unfreezes), and then it may have 2 ways - it may share screen after some time, or it may crash screen-sharing options. I have recorded one of these sharing problems, and during this screencast I can't stop the recording. I don't know what is the reason why it happening, but it starts to happen after I updated to Sequoia, where this overlay for screensharing appeared.

https://www.youtube.com/watch?v=m6mZCo80Dfc

I'm on a Macbook Pro M1Pro running Sequoia 15.5

MacBook Pro 14″, macOS 15.5

Posted on May 21, 2025 4:08 AM

Reply

Answer 1

BDAqua

Level 10

250,673 points

Jun 9, 2025 5:14 AM in response to ProfSpanda

Have you run a Disk First Aid on all drives?

An etrecheck report from both Matt help.

https://etrecheck.com/en/index.html

Reply

Answer 2

etresoft

Level 9

57,596 points

Jun 9, 2025 7:35 AM in response to ProfSpanda

That's clearly a bug in the Discord software. Maybe see if they have an update that is compatible with Sequoia.

Apple has made numerous updates to screen sharing login the past couple of years and 3rd party apps really struggle to keep up. Typically, they refuse to do anything until their software physically stops working. Only then will they begin porting to the new APIs that Apple had released the year before.

What this means is that if you are a heavy user of 3rd party screen sharing software, you must keep your operating system at least 1 year behind in updates.

Reply

Answer 3

leroydouglas

Level 10

201,214 points

May 25, 2025 1:21 PM in response to ProfSpanda

ProfSpanda wrote:

Hello, I'm reopening an issue perfectly described by another user which has been closed without any answer.

I'm on a Macbook Pro M1Pro running Sequoia 15.5

posting a reference link to the "issue perfectly described by another use" may help understand more clearly...(?)

the screen recording was too frenetic for me too decipher anything useful.

I can not say anything about third party issues here:

"D̶i̶s̶c̶o̶r̶d̶,̶ ̶G̶o̶o̶g̶l̶e̶ ̶C̶h̶r̶o̶m̶e̶/̶F̶i̶r̶e̶f̶o̶x̶, Safari, T̶e̶l̶e̶g̶r̶a̶m̶,̶ ̶e̶t̶c̶"

I don't know what is the reason why it happening, but it starts to

happen after I updated to Sequoia, where this overlay for screensharing

appeared.

To be proactive you can file a bug report / submit your Apple Feedback here: Product Feedback - Apple

Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple Support - Apple Support

Reply

Answer 4

ProfSpanda Author

Level 1

8 points

Jun 9, 2025 5:00 AM in response to leroydouglas

The issue posted by the other user is literally the same I posted. I copy pasted it.

I'm not going to call apple for an issue seemingly nobody else except the original user has reported. The issue persists and it's very annoying.The screen recording shows the exact issue described in the post.

I'm not going to call apple for an issue seemingly nobody else except the original user has reported. The issue persists and it's very annoying.

Reply