Deadlock client designer

Hello,
I don’t know if this is the proper channel but I would like to report a deadlock, the dump is attached.

Same deadlock in 8.1.1 and 8.1.3

deadlock.txt (93.3 KB)

part of interest is:

Found one Java-level deadlock:
=============================
"AWT-Windows":
  waiting to lock monitor 0x000000002b67d400 (object 0x0000000703bb0a50, a java.util.logging.ConsoleHandler),
  which is held by "DesignerExecEngine-2"
"DesignerExecEngine-2":
  waiting to lock monitor 0x000000002cb14700 (object 0x0000000703192cd0, a java.io.PrintStream),
  which is held by "AWT-EventQueue-0"
"AWT-EventQueue-0":
  waiting to lock monitor 0x000000002b67d400 (object 0x0000000703bb0a50, a java.util.logging.ConsoleHandler),
  which is held by "DesignerExecEngine-2"

I solved it by setting -Djavaws.ignition.debug to false instead of true, in the jvm param of the designer launcher.

Of course I can not debug anymore, which is quite another problem

Best Regards,

This is not the proper channel. You should open a support ticket. Or you can wait for some random IA employee wandering through the forum to pick it up for you. But they might not. (This forum is not official support.)

1 Like

I’ll open an issue but if you can still go through support if you want.

2 Likes

Heh. Not so random at this time of day… :grin:

2 Likes