Home/ Questions/Q 4242058
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T03:23:30+00:00

It is said that Swing toolkit is not multithread-Safe? What is meant by this

  • 0

It is said that “Swing toolkit is not multithread-Safe?

What is meant by this statement?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Check this link: http://www.jguru.com/faq/view.jsp?EID=131370

    So to simplify the implementation of
    Swing library they chose it to be not
    thread safe. The argument being that
    most of the GUI related work happens
    in the callbacks from the GUI which
    happen on the single GUI thread
    anyways. Granted – for long running
    tasks the user will have to do more
    work if he/she wants to do
    multithreaded activity…

    Specially the link given for the jfc.

    And the this link: http://www.it.uu.se/edu/course/homepage/devgui/vt03/out/ThreadsAndSwing.pdf

    After Swing components have been
    displayed on the screen, they should
    only be operated on by the
    event-handling thread. The
    event-handling thread (or just event
    thread) is started automatically by
    the Java VM when an application has a
    graphical interface. The event thread
    calls methods like paint() on
    Component, actionPerformed() on
    ActionListener, and all of the other
    event-handling methods

    ADD

    Check the second link I have given, specially the section: The Need for Worker Threads in a GUI Setting (also there is an example for explaining it). Quoting here for reference:

    The event thread plays a critical role
    in an application with a graphical
    interface. Code that will be executed
    by the event-handling thread should be
    relatively brief and nonblocking. If
    the event-handling thread is blocked
    in a section of code for a while, no
    other events can be processed!

    • 0