JDK-8267819 : CoInitialize/CoUninitialize should be called on same thread
  • Type: Bug
  • Component: javafx
  • Sub-Component: media
  • Affected Version: 8u311,openjfx17
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2021-05-27
  • Updated: 2021-08-19
  • Resolved: 2021-06-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 Other
8u311Fixed openjfx11.0.13Fixed
Related Reports
Relates :  
JDK-8264737 - JavaFX media stream stops playing after reconnecting via Remote Desktop
Description
JDK-8264737 introduced new code for audio device removal/arrival notifications which calls CoInitialize/CoUninitialize on separate threads. CoInitialize/CoUninitialize should be called on same thread. Calling CoUninitialize on separate threads will result in unitializing COM objects on this thread and if other code runs on such thread it will not work correctly if it is using COM objects.
Comments
Changeset: 47700d8e Author: Alexander Matveev <almatvee@openjdk.org> Date: 2021-06-03 21:47:26 +0000 URL: https://git.openjdk.java.net/jfx/commit/47700d8ef0175d4b457bb658371d2da4ec0a8181
03-06-2021
Raising to P2, since this can sometimes cause a crash.
27-05-2021