Occasionally, after connecting or disconnecting an external monitor on Windows 
10, NetBeans becomes unresponsive.

Has anyone else experienced this problem?

Some investigation reveals that NetBeans is not really frozen--it's just 
failing to repaint the main window. Entering full screen mode with 
Alt+Shift+Enter, and then existing full screen mode again fixes the problem. 
But most users won't discover this. Resizing the window doesn't help--it will 
just show black areas where new repaints should have been done. It's almost 
certainly a JDK bug, because another Java application (jEdit) also ends up in 
the same state, in the same cases. I have not been able to reproduce the 
problem consistently yet.

I'm mainly trying to figure out if it would be worth implementing a workaround.

-- Eirik

Reply via email to