# 8.1.46 pulled, 8.1.47 Emergency Release

**URL:** <https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920>\
**Category:** Ignition\
**Created:** [February 26, 2025, 5:58pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920 "2025-02-26T17:58:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sreis](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sreis/32/14631_2.png) [@sreis](https://forum.inductiveautomation.com/u/sreis)\
**Post date:** [February 26, 2025, 5:58pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/1 "2025-02-26T17:58:54Z")

</div>

Ignition 8.1.46 has been removed from our website and will be replaced with 8.1.47 soon.  
A change was made to fix issues with scripts being accidentally loaded multiple times during initialization, but in certain edge cases that fix can cause a deadlock. At this time we have decided to revert the changes and attempt another fix for the original issue.

---

<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:** [February 26, 2025, 6:00pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/2 "2025-02-26T18:00:51Z")

</div>

Awww!

Curious how closely the broken fix followed my advice...

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 26, 2025, 6:21pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/3 "2025-02-26T18:21:15Z")

</div>

lol, it was absolutely our attempt to fix your scripting bug that caused this. We've reverted it for 8.1.47.

---

<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:** [February 26, 2025, 6:28pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/4 "2025-02-26T18:28:15Z")

</div>

Right, I know that. In my bug report, I provided a suggested solution. I obviously don't know if my suggestion was followed, or found to be flawed.

I recommended serializing/synchronizing/locking on the project script manager. If that wasn't done, it would almost certainly deadlock in some cases. If it was done, and there is still a deadlock possibility, I'm **really** interested in how that happens.

In my initial, detailed, report, I mentioned a "naïve" solution. That solution would _ **seem** _ to solve the problem for my equally naïve reproducer.

---

<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:** [February 26, 2025, 7:06pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/5 "2025-02-26T19:06:54Z")

</div>

It wasn't your exact suggestion, but it was a reentrant lock held by the script manager around most operations in `ScriptModule`, so broadly similar and should've achieved the same end result. So far we've only had one customer report issues, so it seems to be a pretty marginal edge case, but it's bad enough and unknown enough that pulling it was the right move.

---

<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:** [February 26, 2025, 7:08pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/6 "2025-02-26T19:08:18Z")

</div>

> [@paul-griffith](#):
>
> around most operations

So, could be deadlock between a script init and some other operation?

---

<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:** [February 26, 2025, 8:30pm UTC](https://forum.inductiveautomation.com/t/8-1-46-pulled-8-1-47-emergency-release/102920/7 "2025-02-26T20:30:57Z")

</div>

A little birdie showed me the deadlock details.

My suggested solution didn't account for the fact that python/jython aggressively locks around any use of the `import` keyword, using _ **its own lock** _.

Sigh. Busted. 🤦‍♂️

Fortunately, using Jython's own lock for project script auto-loading is likely the right solution. Probably. Hopefully. 🤞
