# Need guide on how to interpret this NonResponsiveEDT files

**URL:** <https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [July 18, 2024, 3:31am UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370 "2024-07-18T03:31:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lester\_Lecong](https://avatars.discourse-cdn.com/v4/letter/l/90db22/32.png) [@Lester\_Lecong](https://forum.inductiveautomation.com/u/Lester_Lecong)\
**Post date:** [July 18, 2024, 3:31am UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370/1 "2024-07-18T03:31:49Z")

</div>

Hello Everyone,  
Good day.  
We have this right-click functionality in Vision. The pop-up sometimes takes time to appear and it outputs the NonResponsiveEDT json file. I have trouble interpreting it to solve the problem and don't know where to start looking.

Can someone guide me how to review these files? I would really appreciate for the help.

Thank you.

Best Regards,  
Lester

[NonResponsiveEdt-2024-07-17\_213022.json](https://forum.inductiveautomation.com/uploads/short-url/gJHiKTcpyso9UpGnZS1LHXvVesh.json) (40.5 KB)  
[NonResponsiveEdt-2024-07-17\_214729.json](https://forum.inductiveautomation.com/uploads/short-url/1JHBiCuzLvjy3vH7r8EbgBDErrq.json) (43.2 KB)  
[NonResponsiveEdt-2024-07-17\_214806.json](https://forum.inductiveautomation.com/uploads/short-url/iDJxH5GBRSYwC5iPeIzosWdJ8xx.json) (46.3 KB)  
[NonResponsiveEdt-2024-07-17\_214824.json](https://forum.inductiveautomation.com/uploads/short-url/gP3nGZsyQvc3HHttCttYV8oO0Lx.json) (43.2 KB)  
[NonResponsiveEdt-2024-07-17\_215651.json](https://forum.inductiveautomation.com/uploads/short-url/fLXGjNlumPEu8N17cZJZ05cAl9U.json) (46.3 KB)  
[NonResponsiveEdt-2024-07-17\_214743.json](https://forum.inductiveautomation.com/uploads/short-url/yWXkWLhElUFaZYbmFfkHfeRuCCJ.json) (43.2 KB)

---

<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:** [July 18, 2024, 12:13pm UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370/2 "2024-07-18T12:13:13Z")

</div>

You have code scattered in your UI events that are performing complex operations, including callouts to gateway RPC.

I didn't look at them all them all, but one was stuck in a Vision windowOpened event (line 48), and the second was stuck in a mouseReleased event (at `shared.graph_functions:163`) waiting on some callout to tag information.

All UI events, especially in Vision, need to be programmed with UI delays in mind--nothing should take more than 100ms. To achieve this, avoid any network-dependent operation. Such operations should use bindings that don't impact the UI thread. (Named query bindings and tag bindings, in particular.) Then the scripts can just access the target of the bindings, for no delay.

Other operations that have no asynchronous binding should be delegated to an asynchronous thread that doesn't touch the UI itself.

An exception would be a "save" or "commit" operation on a button's actionPerformed event. Users expect slightly longer delays for such button actions.

---

<div class="post-metadata">

**Author:** ![Lester\_Lecong](https://avatars.discourse-cdn.com/v4/letter/l/90db22/32.png) [@Lester\_Lecong](https://forum.inductiveautomation.com/u/Lester_Lecong)\
**Post date:** [September 5, 2024, 2:06am UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370/3 "2024-09-05T02:06:41Z")

</div>

Hello pturmel,

Thank you for your help. Sorry for the late reply.  
By the way, how do you analyze these thread dumps? I want to know the processes, so that I can work on my own when new issue arise.

Best Regards,  
Lester

---

<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:** [September 5, 2024, 12:22pm UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370/4 "2024-09-05T12:22:20Z")

</div>

You study the stack trace of the thread named "AWT-EventQueue-0" or similar.

---

<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:** [September 5, 2024, 3:16pm UTC](https://forum.inductiveautomation.com/t/need-guide-on-how-to-interpret-this-nonresponsiveedt-files/93370/5 "2024-09-05T15:16:11Z")

</div>

You can open the thread dump JSON files in Kindling for a nicer presentation:

> [@Kindling - a collection of tools to help with Ignition](https://forum.inductiveautomation.com/t/kindling-a-collection-of-tools-to-help-with-ignition/54689):
>
> Happy new year, and all that! I wanted to debut for the community something I've been working on for a little while, and hopefully it's useful to somebody out there. The full story: Long ago I worked as a support rep at IA. While there, I made some tools for internal use; Vision windows attached to an internal gateway that knew how to parse our log IDB files and thread dump files and display them in a more useful way. Recently, I had some downtime, and wanted to take on a new project, so I recr…

But there really is no replacement for hard-won domain knowledge here. As Phil stated - look at the EventQueue thread, look at the stacktrace, and piece together what it was doing at the time.
