List Icon
Archive de la liste de diffusion

La liste de diffusion est fermée depuis juillet 2022, mais sert toujours d'archive d'informations sur QF-Test.
Cependant, si vous souhaitez rester informé des nouveautés concernant QF-Test, vous pouvez simplement vous
abonner à la newsletter 

our obtenir des informations à jour sur chaque version - y compris les versions mineures - vous pouvez
nous pouvez vous abonner au flux RSS ou nous suivre sur les médias sociaux.
Alternativement, QF-Test fournit également des informations sur la version elle-même.

Une autre source d'information est notre blog, qui contient des articles actuels sur des thèmes généraux, sur l'entreprise QFS et aussi divers "how-tos", veuillez vous
ABonner au Blog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] Problem with Swing lockup

  • Subject: [QF-Test] Problem with Swing lockup
  • From: STEPHENS Patrick <patrick.stephens@?.com>
  • Date: Thu, 24 Jan 2013 17:25:26 +0000

Hi all,
I thought I had modified my test application to use SwingUtilities.invokeAndWait() when creating its JFrame but I am still seeing a lockup when it is launched from QFTest.
 TestHCIMain(String[] args)
  try {
   javax.swing.SwingUtilities.invokeAndWait( new Runnable() {
    public void run() {
     jFrame = getJFrame();
   } );
 public static void main(String[] args)
  System.out.println("TestHCIMain started");
  for(int i = 0; i < args.length; ++i)
  new TestHCIMain(args);
This gives me a thread dump with the usual Swing thread safety culprit: java.awt.Component$AWTTreeLock
It looks like my invokeAndWait call has been triggered on a QFTest thread:
 at com.thalesgroup.sat.toolbar.test.TestHCIMain.getJFrame(
 at com.thalesgroup.sat.toolbar.test.TestHCIMain.access$100(
 at com.thalesgroup.sat.toolbar.test.TestHCIMain$
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at de.qfs.lib.gui.EventQueue.doDispatch(
 at de.qfs.apps.qftest.client.awt.dd.doDispatch(SourceFile:439)
 at de.qfs.lib.gui.EventQueue.dispatchEvent(
 at de.qfs.apps.qftest.client.awt.dd.a(SourceFile:350)
 at Method)
 at de.qfs.apps.qftest.client.awt.dd.dispatchEvent(SourceFile:332)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at Source)
Anyone seem anything obvious I've missed?

Patrick Stephens
Software Engineer

Thales UK
Dolphin House, Ashurst Drive
Cheadle Heath, Stockport SK3 OXB - UK

Tel: +44 (0)161 741 3860
e-mail: patrick.stephens@?


Please consider the environment before printing a hard copy of this e-mail.

The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)1932 824800 and delete it and all copies from your system.

Thales Corporate Services Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 959962.  

Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273


Attachment: jstack_testhci.log
Description: jstack_testhci.log