# Clicking on the Tag Diagnostic button locks up the Designer?

**URL:** <https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133>\
**Category:** Ignition\
**Created:** [January 21, 2025, 1:07am UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133 "2025-01-21T01:07:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [January 21, 2025, 1:07am UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/1 "2025-01-21T01:07:27Z")

</div>

v8.1.43  
Windows 10

I've noticed, after upgrading from 8.1.17, that whenever I click on the new tag diagnostic button, the designer locks up (the dialogue doesn't show up, and I can't click on anything in the Designer. Resizing the designer doesn't repaint the designer and shows black)..

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/e/be4aed6c6bdde68250b6375870cd3665567681fe.png)

I've tried accessing it from the tag editor as well as the context menu on the tag in the tag browser, both lock it up seemingly indefinitely - I've left it a good few minutes, i'll keep it running to see if it comes good.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/4/24a992613bc077c2e310fb9b58878ee1aef6f82f.png)

The Gateway has ~500k tags with a front/backend gateway architecture, so it's a moderately large project, and I'm accessing it across a VPN.

Has anyone else had this issue? Wondering if it's a bug

Edit: After 10-20 mins it finally showed up... Note: I have the tag reference tracker turned _off_

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 28, 2025, 11:55pm UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/2 "2025-01-28T23:55:12Z")

</div>

Are you getting "NonResponsiveEDT" automatic thread dumps during this period? If you are, it'd be helpful to see those.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [January 31, 2025, 12:21am UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/3 "2025-01-31T00:21:51Z")

</div>

[NonResponsiveEdt-2025-01-31\_104906.json](https://forum.inductiveautomation.com/uploads/short-url/xKeRnPtY5j7KttUrgeGZc2oQAxY.json) (81.0 KB)

Yep!  
(for others trying to find the designer logs, they're under (windows)  
`C:\Users\<username>\.ignition\cache\gw<gateway hostname/ip>_<port>)\C#`)

I'm expecting it to be due to reaching out to network drives that may not be connected, but I can't decipher stack traces like these...

Edit:  
a bit cheeky to add to this thread, but I have this non-resp-edt as well after trying to open a named query in the designer. wondering what caused it. Designer did eventually come good after several minutes  
[NonResponsiveEdt-2025-01-31\_113424.json](https://forum.inductiveautomation.com/uploads/short-url/d2nEIzb58aMJu265Pce5lT1AWip.json) (103.2 KB)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 31, 2025, 4:41pm UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/4 "2025-01-31T16:41:20Z")

</div>

> [@nminchin](#):
>
> I'm expecting it to be due to reaching out to network drives that may not be connected, but I can't decipher stack traces like these...

Oof. This is unfortunate.

This whole trace:

```stacktrace
"java.base@17.0.13/jdk.internal.misc.Unsafe.park(Native Method)",
"java.base@17.0.13/java.util.concurrent.locks.LockSupport.park(Unknown Source)",
"java.base@17.0.13/java.util.concurrent.FutureTask.awaitDone(Unknown Source)",
"java.base@17.0.13/java.util.concurrent.FutureTask.get(Unknown Source)",
"java.desktop@17.0.13/sun.awt.shell.Win32ShellFolderManager2$ComInvoker.invoke(Unknown Source)",
"java.desktop@17.0.13/sun.awt.shell.ShellFolder.invoke(Unknown Source)",
"java.desktop@17.0.13/sun.awt.shell.ShellFolder.invoke(Unknown Source)",
"java.desktop@17.0.13/sun.awt.shell.Win32ShellFolder2.getIcon(Unknown Source)",
"java.desktop@17.0.13/javax.swing.filechooser.FileSystemView.getSystemIcon(Unknown Source)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI$2.getListCellRendererComponent(SyntheticaFileChooserUI.java:368)",
"java.desktop@17.0.13/javax.swing.plaf.basic.BasicListUI.updateLayoutState(Unknown Source)",
"java.desktop@17.0.13/javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(Unknown Source)",
"java.desktop@17.0.13/javax.swing.plaf.basic.BasicListUI$Handler.valueChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.fireValueChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.changeSelection(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.changeSelection(Unknown Source)",
"java.desktop@17.0.13/javax.swing.DefaultListSelectionModel.setSelectionInterval(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JList.setSelectedIndex(Unknown Source)",
"java.desktop@17.0.13/javax.swing.plaf.basic.BasicComboPopup.setListSelection(Unknown Source)",
"java.desktop@17.0.13/javax.swing.plaf.basic.BasicComboPopup$Handler.itemStateChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JComboBox.fireItemStateChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JComboBox.selectedItemChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JComboBox.contentsChanged(Unknown Source)",
"java.desktop@17.0.13/javax.swing.AbstractListModel.fireContentsChanged(Unknown Source)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI$DirectoryComboBoxModel.setSelectedItem(SyntheticaFileChooserUI.java:1459)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI$DirectoryComboBoxModel.addItem(SyntheticaFileChooserUI.java:1439)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI$DirectoryComboBoxModel.access$0(SyntheticaFileChooserUI.java:1366)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI.doDirectoryChanged(SyntheticaFileChooserUI.java:1200)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI.access$19(SyntheticaFileChooserUI.java:1173)",
"de.javasoft.plaf.synthetica.filechooser.SyntheticaFileChooserUI$8.propertyChange(SyntheticaFileChooserUI.java:1058)",
"java.desktop@17.0.13/java.beans.PropertyChangeSupport.fire(Unknown Source)",
"java.desktop@17.0.13/java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)",
"java.desktop@17.0.13/java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)",
"java.desktop@17.0.13/java.awt.Component.firePropertyChange(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JFileChooser.setCurrentDirectory(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JFileChooser.<init>(Unknown Source)",
"java.desktop@17.0.13/javax.swing.JFileChooser.<init>(Unknown Source)",

```

Is out of our hands. In summary, the file chooser we're trying to show you to choose an export location:

```stacktrace
"com.inductiveautomation.ignition.client.script.ClientFileUtilities.getChooser(ClientFileUtilities.java:35)",
"com.inductiveautomation.ignition.designer.gui.import_export.ProjectExporter$ExportPanel.saveExportToDisk(ProjectExporter.java:403)",

```

Is trying to render the file system icons using an appropriate icon from the system, and ultimately doing that with a native Windows method invoked via COM:

```python
"java.desktop@17.0.13/sun.awt.shell.Win32ShellFolderManager2$ComInvoker.invoke(Unknown Source)",

```

I feel like I saw this before in support, and for whatever reason the JDK has no timeout on this COM request 😬

Oh, just kidding, found the support thread, the timeout is 1 **day** :

> <https://github.com/openjdk/jdk/blob/fcd5ebc7e8964c7936c0eede031cb6193621f5fb/src/java.desktop/windows/classes/sun/awt/shell/Win32ShellFolderManager2.java#L506>

Unfortunately there's not much for us to do about this; it's code that's out of our direct control.

> [@nminchin](#):
>
> a bit cheeky to add to this thread,

Same story in that thread dump 😬

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 31, 2025, 4:46pm UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/5 "2025-01-31T16:46:18Z")

</div>

`Win32ShellFolderManager2.java`

Mwah, ha, ha, ha! 🤣

Sorry Nick, but another one to add to my list.

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [February 1, 2025, 12:08am UTC](https://forum.inductiveautomation.com/t/clicking-on-the-tag-diagnostic-button-locks-up-the-designer/101133/6 "2025-02-01T00:08:36Z")

</div>

Happy to help, Phil! 🤣

> [@paul-griffith](#):
>
> Oh, just kidding, found the support thread, the timeout is 1 **day** :

Well that's a long coffee break!  
Good to at least know the cause of the errors though, cheers
