Bug 230917 – Crash in WebKit::DisplayLink::displayLinkCallback()

• Component: New Bugs
• Status: RESOLVED FIXED

[Simon Fraser (smfr)]

Crash in Crash in WebKit::DisplayLink::displayLinkCallback()

[Simon Fraser (smfr)]

Created attachment 439521 [details]
Patch

[Simon Fraser (smfr)]

<rdar://problem/82528370>

[Tim Horton]

Comment on attachment 439521 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=439521&action=review

> Source/WebKit/UIProcess/mac/DisplayLink.cpp:51
> -        WTFLogAlways("Could not create a display link for display %u: error %d", displayID, error);
> +        WTFLogAlways("DisplayLink: Could not create a display link for display %u: error %d", displayID, error);

Is this disastrous enough that it should be a simulated crash?

[Simon Fraser (smfr)]

Created attachment 439537 [details]
Patch

[EWS]

Committed r283209 (242251@main): <https://commits.webkit.org/242251@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 439537 [details].

[Sam Sneddon [:gsnedders]]

*** Bug 232502 has been marked as a duplicate of this bug. ***

[Brad Andalman]

I really hope this is our bug, and am happy to see that (if it is) it has already been fixed.

That said, this bug is affecting some of our uses pretty significantly right now. Is there anything we can do on our end that makes it less likely to hit this bug?