{"push_id":2829860895,"size":1,"distinct_size":1,"ref":"refs/heads/monocle-crash-2","head":"51d1df779024b6ba148f0497bf20ec9d5112295e","before":"8b484dfab1c8962854ebc81482bcb7475d151b38","commits":[{"sha":"51d1df779024b6ba148f0497bf20ec9d5112295e","author":{"name":"Michael Ennen","email":"2a303560a77e4a2f64b70ec418aeb63cef04e8a1@gmail.com"},"message":"JDK-8201539: Fix DirectWrite crash on Monocle.\n\nCOM (aka OLE) is initialized in two places, at the creation of a\nWinApplication and in directwrite.cpp when IWICImagingFactory is\ncreated for the first time.\n\nThe IWICImagingFactory initialization in directwrite.cpp initializes\nCOM, creates an IWICImagingFactory instance, and then uninitializes COM.\n\nWhen Monocle's HeadlessPlatform is used calling the CreateBitmap method\nof IWICImagingFactory causes a crash. Without Monocle, on the normal\nWinPlatform, calling CreateBitmap does *not* cause a crash. In both\ncases COM should be un-initialized by the IWICImagingFactory\ninitialization method.\n\nWhat accounts for the difference?","distinct":true,"url":"https://api.github.com/repos/brcolow/openjdk-jfx/commits/51d1df779024b6ba148f0497bf20ec9d5112295e"}]}
{"actor":{"display_login":"brcolow"}}