JDK-8229394 : JavaFx UI Window non responsive and black on Remote Desktop Connection.
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: openjfx12
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: windows_10
  • CPU: x86_64
  • Submitted: 2019-08-10
  • Updated: 2021-02-25
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8118805 - Nothing displayed when you RDP to a machine running a JavaFX app
Relates :  
JDK-8256439 - Disconnecting from the RDP GUI interface of Java FX applications stop rendering
Relates :  
JDK-8239589 - JavaFX UI will not repaint after reconnecting via Remote Desktop
Description
ADDITIONAL SYSTEM INFORMATION :
OS : Windows 10
Resolution of system running javafx application : 1080p
Resolution of system taking RDP : 1080p
Pixel Density : Same for both systems


A DESCRIPTION OF THE PROBLEM :
A JavaFx Application working fine when opened on console and then System is accessed remotely via RDP, the JavaFx Window is unresponsive and completely black over RDP.
 

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Open javafx application on System-1.
2. Access System-1 form System-2 via RDP.


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The JavaFx application should be accessible over RDP.
ACTUAL -
Non responsive and black javafx window.

CUSTOMER SUBMITTED WORKAROUND :
Tried changing color16/24/32 and connection quality. No Workaround.

FREQUENCY : always
Comments
With Windows 10, we are getting HW acceleration over RDP, so this might work once JDK-8239589 is fixed. We should test it at that time.
25-02-2021
I note that if forcing the SW pipeline does allow the application to run, then this is almost certainly the known limitation that the Prism hardware-accelerated pipeline, does not work over RDP.
16-08-2019
This might be the same issue as JDK-8118805, which we closed as "Won't fix", although I'll leave this one open. A possible workaround, as indicated in that bug, is to force the software pipeline by running with: java -Dprism.order=sw
16-08-2019