Home/ Questions/Q 154863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T10:03:15+00:00

There are many methods you shouldn’t call if you are not on the AWT

  • 0

There are many methods you shouldn’t call if you are not on the AWT event thread. These are generally methods that manipulate the UI in some way.

Is this the case with Component’s getGraphicsConfiguration(…)? It is only a getter but it appears to cause a deadlock if the event thread is waiting on the thread calling this method.

Whilst solving the deadlock is fairly trivial (avoid using wait or synchronize on the event thread), should I only be calling getGraphicsConfiguration in a Runnable passed to SwingUtilities.invokeLater(…) or invokeAndWait(…)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. AWT thread-safety is (necessarily) broken. Just don’t go anywhere near it. Stay on the straight AWT EDT

    Also note that just because a method is in java.awt.Component, it does not mean that the object (or an object referenced by it) is not in Swing and therefore really not even pretending to be thread-safe at all. (Enough nots?)

    • 0