Severe screen tearing in Roblox player (Regression)

[DaDude_89 (KasCode)]

Since about one day ago (24/11/2025), I’ve been noticing severe screen tearing seemingly caused by the Roblox player. I am using a MacBook, and have tested on my laptop display as well as an external display and have seen the same results.

I previously reported this issue earlier this month, and it was fixed then. It has started occurring again. All the details about it are the same as detailed in the previous bug report:

Severe screen tearing in Roblox Player, not display-specific

Since about two days ago (07/09/2025), I’ve been noticing severe screen tearing seemingly caused by the Roblox player. I am using a MacBook, and have tested on my laptop display as well as an external display and have seen the same results. The issue does not seem to be display specific, I have tested on two so far The issue does not occur in other games (tested with Minecraft) The issue happens in multiple Roblox games (tested with performance heavy and lighter games) The issue does not happe…

Info from the previous bug report that might be relevant (this has not happened to be yet recently, but was relevant to the previous report):

@DaDude_89

An update on this: recently in performance heavy games my FPS has been dropping to a flat minimum of either 20.0 FPS or 40.0 FPS unpredictably […] I am not sure if this is related to the screen tearing issue, but it does seem like something caused by VSync. Checking the microprofiler, the low FPS is entirely caused by “acquireFrameBuffer”.

Key points about the issue

• It happens on both my laptop display as well as on an external monitor
• It happens across a variety of games, regardless of how resource intensive they are
• It does not happen in other games (eg. Minecraft) or other applications
• I have already tried re-installing and restarting.

System information

[evisceratedpumpkin (PenguinPerson)]

Does this issue still occur? There was a production change that could have cause this issue to happen again on certain Macs.

[DaDude_89 (KasCode)]

I just tested briefly and it was not happening this time. I’m not sure if this is just by chance, I will test more soon.

[DaDude_89 (KasCode)]

After more testing the issue has not occurred since my last reply. To clarify, was there a change that would fix this issue or am I not seeing the issue by chance?

[evisceratedpumpkin (PenguinPerson)]

There was a change that fixed the issue. This problem is unlikely to happen again!