Cannot Fix

Failed to fetch unit options for fuzzy finder

Frderick 3 years ago updated by Lazlo Bonin (Lead Developer) 3 years ago 5


I have the fowling issue with Bolt, that appears in the newest Bolt 2 Alpha and the stable version. Rebuilding the units doesn’t help also reimporting Bolt or even using the version 2 doesn’t solve the issue.

TimeoutException: Time-out exceeded on Unity API thread action delegate. Potential deadlock.

Failed to fetch unit options for fuzzy finder (error log below).
Try re-extracting with 'Tools > Bolt > Extractor'.

System.TimeoutException: Time-out exceeded on Unity API thread function delegate. Potential deadlock.
at Ludiq.UnityAPI.Await[T] (System.Func`1[TResult] func, System.Nullable`1[T] timeout) [0x00091] in G:\Unity Projects\SAGHannoverMesse2019\SAGHannoverMesse2019\Assets\Ludiq\Ludiq.Core\Editor\Utilities\UnityAPI.cs:181
at Ludiq.UnityAPI.Await[T] (System.Func`1[TResult] func) [0x00001] in G:\Unity Projects\SAGHannoverMesse2019\SAGHannoverMesse2019\Assets\Ludiq\Ludiq.Core\Editor\Utilities\UnityAPI.cs:140
at Bolt.UnitOptions.Subset (Bolt.IUnitPort connectionSource, Bolt.UnitOptionFilter filter, Ludiq.GraphReference reference) [0x00049] in G:\Unity Projects\SAGHannoverMesse2019\SAGHannoverMesse2019\Assets\Ludiq\Bolt.Flow\Editor\Options\UnitOptions.cs:28
at Bolt.UnitOptionTree.Prewarm () [0x00031] in G:\Unity Projects\SAGHannoverMesse2019\SAGHannoverMesse2019\Assets\Ludiq\Bolt.Flow\Editor\Options\UnitOptionTree.cs:31
Bolt.UnitOptionTree:Prewarm() (at Assets/Ludiq/Bolt.Flow/Editor/Options/UnitOptionTree.cs:35)
Ludiq.<>c__DisplayClass21_0:b__0() (at Assets/Ludiq/Ludiq.Core/Editor/Interface/Fuzzy/FuzzyWindow.cs:347)
Ludiq.FuzzyWindow:RunTaskSynchronous(Action) (at Assets/Ludiq/Ludiq.Core/Editor/Interface/Fuzzy/FuzzyWindow.cs:1193)
Ludiq.FuzzyWindow:Work() (at Assets/Ludiq/Ludiq.Core/Editor/Interface/Fuzzy/FuzzyWindow.cs:1227)

Bolt Version:
Bolt 2 and 1.4.1
Unity Version:
Scripting Backend:
.NET Version (API Compatibility Level):
Pending Review

Hi Frderick!

Sorry you're experiencing this issue, it's the first time something like this is reported. 

The only thing I can think of that would cause it (in Bolt 1.4, because 2.0 is still unstable so I can't guarantee anything) is that the Unity window would be out of focus when it tries to load. But I'm guessing that's not the case?

Some questions to help me isolate:

  • Does this happen on a blank project?
  • Does this happen every time or just some times?
  • Does this happen with fewer types selected in the Extractor?

Thanks for the replay, please see my answers in bold text.

Tested with version 1.4.1

  • Does this happen on a blank project?
  • No
  • Does this happen every time or just some times?
  • Somtimes (very few times) it is working but i have no idea why 
  • Does this happen with fewer types selected in the Extractor?
  • Yes

Hi Frderick,

Thanks for the reply and sorry for the delay, I was off out of town at GDC.

Can you tell if this happens due to any specific type / third party plugin that is added to the project?

This is the first report of this type I'm getting so I'm not sure what be causing it.

Also, how fast/recent is your computer/CPU?

The error is caused by the PiXYZ PluginWhen i remove this from my project there is no error anymore. 

CPU is an i7 8700k

Cannot Fix

Hi Frdrerick,

So I looked into this, and I can indeed reproduce the issue with the PiXYZ plugin in the project.

What's puzzling is that adding Debug.Log calls to debug where the deadlock happens fixes it.

It seems like an obscure bug in Unity threading and EditorApplication.update, and I'm not sure how to fix it. I'll let the PiXYZ team know about the issue and hope they can shine some light on what in their code might be interacting with it.