# \[Bug-11451\] Deadlock Detected

**URL:** <https://forum.inductiveautomation.com/t/bug-11451-deadlock-detected/21338>\
**Category:** Ignition Early Access\
**Created:** [December 11, 2018, 4:42pm UTC](https://forum.inductiveautomation.com/t/bug-11451-deadlock-detected/21338 "2018-12-11T16:42:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![plarochelle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/plarochelle/32/29608_2.png) [@plarochelle](https://forum.inductiveautomation.com/u/plarochelle)\
**Post date:** [December 11, 2018, 4:42pm UTC](https://forum.inductiveautomation.com/t/bug-11451-deadlock-detected/21338/1 "2018-12-11T16:42:43Z")

</div>

Not sure if this is the proper place but I got the following deadlocked message:  
Deadlock Detected  
The following threads are involved in deadlock: 2056,2070

I’ve attached the thread dump:  
[NeoMatrix Demo\_thread\_dump20181211-113916.txt](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2af37edc11af8e989ea1005b0cc1d5cecbbf31d3.txt) (79.3 KB)

Thanks,  
Pete

---

<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:** [December 11, 2018, 4:58pm UTC](https://forum.inductiveautomation.com/t/bug-11451-deadlock-detected/21338/2 "2018-12-11T16:58:53Z")

</div>

This looks like something we’ve run into a couple times on the demo server - still under investigation internally. Thanks for reporting!

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [January 3, 2019, 4:50pm UTC](https://forum.inductiveautomation.com/t/bug-11451-deadlock-detected/21338/3 "2019-01-03T16:50:31Z")

</div>

This issue was fixed in the build that was uploaded on 12/22. Please let us know if you continue to see this behavior after upgrading.
