🚀 go-pugleaf

It is very different (depending on which JDK version, which Linux 
version), but you should definitely NOT change your code to leave it up 
to the OS in this situation. You just may have not hit the contention in 
Linux yet, and in any event can't depend on that behavior being 
consistent from release to release. Using SwingUtilities insures that 
you won't have a problem by making the single AWT thread responsible for 
updating all the UI, regardless from which thread the original UI 
request came from.

In terms of resources, there is an interesting section in the "Taming 
Java Threads" book by Holub (or go to 
http://www.holub.com/publications/articles/index.html for lots of 
interesting stuff by this guy) on differences in threading between 
Windows and *nix (primarily Solaris, but the issues apply).

Tad Frysinger
[TeamB]

Aleksandar Pecanov wrote:
> I remember that while working on Windows, when I wanted to run a separate
> thread to aupdate a swing component (for example a memory indicator), I
> had run the thread with SwingUtilities.invokeLater(). However, while
> working under Linux, I forgot to use it. The component worked fine. Is
> the implementation of threads and thread synchronization in Java different
> on Windows and Linux. If so, where can I find more information about what
> should I pay attention when developing multiplatform Java Application?
>