Every time my Vision project is started it generates a NonResponsiveEdt file and I can't figure out why. If anybody can have a look at the attached file and provide some insight that would be great.
In the Diagnostics Console it appears straight after starting up:
15:23:10.181 [AWT-EventQueue-0] INFO vision.App - Starting Up...
15:23:13.684 [EDT-Watchdog-1] INFO edt-watchdog - Non-responsive UI thread detected. Stack saved at 'C:\Users\David\.ignition\cache\gwignition_8043\C2\NonResponsiveEdt-2024-05-03_152313.json'
The vision project has been cut right back to a bare minimum to identify the cause and it still happens. There are no scripts, and only a single blank vision page.
NonResponsiveEdt-2024-05-03_152313.json (30.8 KB)
Any help appreciated.
Looks like a bogus report. And therefore a bug worth reporting to support.
Do you have any more of these?
1 Like
Heaps. Here are a few fresh ones created by restarting the vision client project (which has no pages or scripts) from the Ignition Designer
They have more lines in the AWT-EventQueue-0 stacktrace than the last one, and they're all a little different but happen at the same time (immediately after starting up).
Any help appreciated.
09:04:08.563 [ProjectDownloader] INFO Vision.DownloadProjectPane - Starting download of 437 bytes
09:04:08.669 [ProjectDownloader] INFO tags.manager.gwinterface - Tag poll rate changed to 250 ms
09:04:08.670 [ClientExecEngine-1] INFO tags.subscriptions - Changing connected quality to 'Good'
09:04:09.952 [ProjectDownloader] INFO com.inductiveautomation.reporting.client.ReportingClientHook - Starting up Reporting Module. Mode: Activated
09:04:12.358 [AWT-EventQueue-0] INFO vision.App - Starting Up...
09:04:15.731 [EDT-Watchdog-1] INFO edt-watchdog - Non-responsive UI thread detected. Stack saved at 'C:\Users\David\.ignition\cache\gwignition.com_8043\C3\NonResponsiveEdt-2024-05-06_090415.json'
NonResponsiveEdt-2024-05-06_085859.json (32.3 KB)
NonResponsiveEdt-2024-05-06_090041.json (32.8 KB)
NonResponsiveEdt-2024-05-06_090226.json (35.1 KB)
NonResponsiveEdt-2024-05-06_090415.json (34.9 KB)
These are better, thanks.
There's a few areas showing up to investigate. The most suspicious to me is that KeyboardLayoutManager is making a network call to the gateway on the EDT thread during startup. @PGriffith
Whoops. Yeah, that's definitely wrong/unintended. I'll file a ticket to fix.
The other two thread dumps point at Java asking your OS for the MAC address to use, as part of a generating a 'machine ID' in a totally unnecessary way as part of a UUID generation scheme. That's also possibly something we could work around - we don't use the generated IDs for anything that would require them to be useful.
Thanks Kevin and Paul,
Is there anything I can do in the meatime to stop these happening?
Would restarting the gateway or reinstalling Ignition help?
Not really, but you can also just ignore them. They're creating temp files in a directory, but your OS will clean them up eventually.
Basically the gateway is taking "too long" (>2s) to return values, in the keyboard layout case, and your system's taking too long to return MAC address info in the other case.