Bug [Addressables 1.17.13] get_frameCount can only be called from the main thread.

Just updated Addressables from 1.15.1. Trying to launch the game in the Editor in the fast mode.
Getting a bunch of exception in the console:

Code (CSharp):

1. UnityException: get_frameCount can only be called from the main thread.
2. Constructors and field initializers will be executed from the loading thread when loading a scene.
3. Don't use this function in the constructor or field initializers, instead move initialization code to the Awake or Start function.
4. UnityEngine.AddressableAssets.Utility.ResourceManagerDiagnostics.OnResourceManagerDiagnosticEvent (UnityEngine.ResourceManagement.ResourceManager+DiagnosticEventContext eventContext) (at Library/PackageCache/com.unity.addressables@1.17.13/Runtime/Utility/ResourceManagerEventCollector.cs:95)
5. UnityEngine.ResourceManagement.ResourceManager.PostDiagnosticEvent (UnityEngine.ResourceManagement.ResourceManager+DiagnosticEventContext context) (at Library/PackageCache/com.unity.addressables@1.17.13/Runtime/ResourceManager/ResourceManager.cs:303)
6. UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationBase`1[TObject].IncrementReferenceCount () (at Library/PackageCache/com.unity.addressables@1.17.13/Runtime/ResourceManager/AsyncOperations/AsyncOperationBase.cs:145)
7. UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationBase`1+<>c__DisplayClass45_0[TObject].<get_Task>b__0 (System.Object o) (at Library/PackageCache/com.unity.addressables@1.17.13/Runtime/ResourceManager/AsyncOperations/AsyncOperationBase.cs:248)
8. System.Threading.Tasks.Task`1[TResult].InnerInvoke () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
9. System.Threading.Tasks.Task.Execute () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
10. --- End of stack trace from previous location where exception was thrown ---
11. System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
12. System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
13. System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
14. System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
15. System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
16. Services.AddressableHelper+<LoadAssetAsync>d__4`1[T].MoveNext () (at Assets/Scripts/Services/AddressableHelper.cs:47)
17. --- End of stack trace from previous location where exception was thrown ---
18. System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
19. System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
20. System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
21. System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
22. System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
23. Services.SpriteCache+<Load>d__10.MoveNext () (at Assets/Scripts/Services/Cache/SpriteCache.cs:61)
24. --- End of stack trace from previous location where exception was thrown ---
25. System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () (at <eae584ce26bc40229c1b1aa476bfa589>:0)
26. System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state) (at <eae584ce26bc40229c1b1aa476bfa589>:0)
27. UnityEngine.UnitySynchronizationContext+WorkRequest.Invoke () (at <42a5878ce129403083acccf18e43363f>:0)
28. UnityEngine.UnitySynchronizationContext:ExecuteTasks()
29.  

 

I am seeing the same thing. For me I can't do any LoadAssetAsync calls (or really anything) with Addressables because of this.

 

I've had the same issue after upgrading to 1.17.13 and all it took to get this exception was instantiating something. The exception is no longer thrown when the Send Profiler Events setting is disabled, so that's what I'm doing until this is fixed.

 

Oh, thanks for the tip Mark, i'll try that. I wish Addressables quality control was a bit better! Upgrading Addressables is always an incredible pain due to major bugs.

 

Yes, every single update is a pain. Every time something breaks.

 

I get the same error if I use await handle.task, if I use yield or WaitForCompletion() I don't get it

 

Reproduced in 1.17.15

 

also running into this into the editor, doesn't matter if I turn off profiler events in the addressables settings

 

I use addressables like a year or more and all the time every update is the same. You try to fix bug create new bugs, ask peoples send reports. Its not like a hard to test bug, but it seems like package is not testing before release, and make tests on real users. Maybe you shoud test package harder cause it hurts for games with million player wait when some minor bug will be fixed, and risk on real players when update plugin

P.S. OMG you even remove preview mark from plugin, when users cant even use plugin, and get errors like that its not look like stable version (1.17.15)

 

Hello, does someone have an update on this? Its would be really nice to have that fixe soon. Sync remove a LOT of complexity in our app.

 

Thank you for the clarification!

 

Agree! so many pain while using addressable.

 

Nothing scares me as much as Addressables updates. Either it's some bug or a functionality has changed drastically (again).
I get this bug in 1.17.17. It's marked as a Release version, but it really shouldn't.

 

Lol each addressable version is a new adventure... you get new bug, some fix, some old bug that show back... when you are lucky you even get process change...
1.17.17 with slight modification do what I need at the moment. not doing any upgrade or touching it again unless found something that break it, and that I can't fix myself using their code

 

I found that profiler event change only if you build the addressable.

 

Hello, 1.18.2 has release but the bug is not fixed yet. When will this be fixed?

 

@unity_bill Will there be a new 1.17.x release with this fix included? Currently 1.18.4 is unusable in our project due to the bug described in this post:
https://forum.unity.com/threads/ass...s-awake-onenable-and-ondestroy-twice.1109402/

 

Just stumbled across this in 1.17.17 as-well while trying to debugging reference counts. Disable the events and rebuilding Addressables made it work again for now.