New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Call to GSFontInitialize() #9705
Remove Call to GSFontInitialize() #9705
Conversation
EWS run on previous version of this PR (hash 971c2d1) |
971c2d1
to
56b1ed9
Compare
EWS run on previous version of this PR (hash 56b1ed9) |
56b1ed9
to
976169d
Compare
EWS run on previous version of this PR (hash 976169d) |
https://bugs.webkit.org/show_bug.cgi?id=251807 <rdar://problem/32886715> Reviewed by NOBODY (OOPS!). Now that <rdar://problem/32886715> has been addressed, we can remove this function call. So basically, revert commit 5bea31a *Source\WebCore\PAL\pal\spi\ios\GraphicsServicesSPI.h: *Source\WebCore\page\cocoa\MemoryReleaseCocoa.mm:
@cdumez Do you think we can merge this one? |
976169d
to
508f25c
Compare
EWS run on current version of this PR (hash 508f25c) |
Where do you see that rdar://problem/32886715 was addressed? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't believe we can safely remove the call to GSFontInitialize()
. As far as I can tell, the underlying framework retains the behavior present when @cdumez added this code, and I see no reason why it would be safe to remove it.
If you know that this bug was fixed through some change other than rdar://problem/32886715, please let me know and I'll happily support removing it!
Thank you!
508f25c
508f25c