Repeated errors when loading Spine resources multiple times

FSL

In my own unity game, after loading Spine resources several times (such as repeatedly opening the window of the interface), there will be a large number of "AABB" related errors. The resources are very large (usually 8192 * 8192px, sometimes may be several). I haven't had any problems in the past, and I can't confirm where the problem occurred at the moment. Could you please help me take a look? Thank you very much.

Unity Console Error：

Invalid worldAABB. Object is too large or too far away from the origin.
0x00007FF63F4CCA1C (Unity) StackWalker::GetCurrentCallstack
0x00007FF63F4D09C1 (Unity) StackWalker::ShowCallstack
0x00007FF63DAE98F5 (Unity) GetStacktrace
0x00007FF64019734E (Unity) DebugStringToFile
0x00007FF640197062 (Unity) AssertImplementation
0x00007FF63EC755DF (Unity) MeshRenderer:: DispatchUpdate
0x00007FF63F0E9070 (Unity) BatchJob
0x00007FF63ED7A921 (Unity) JobQueue::Exec
0x00007FF63ED7B07D (Unity) JobQueue::ExecuteJobFromHighPriorityStack
0x00007FF63ED7CC73 (Unity) JobQueue:: ProcessJobs
0x00007FF63ED8231F (Unity) JobQueue::WorkLoop
0x00007FF63F2DD423 (Unity) Thread::RunThreadWrapper
0x00007FF98D907614 (KERNEL32) BaseThreadInitThunk
0x00007FF98EEA26A1 (ntdll) RtlUserThreadStart

Harald

FSL In my own unity game, after loading Spine resources several times (such as repeatedly opening the window of the interface), there will be a large number of "AABB" related errors.

I'm afraid I don't quite understand what you mean by "loading Spine resources several times" and by "repeatedly opening the window on the interface". Do you mean that you have a UI window where your Spine skeletons are contained in, and you open several windows of this type at the same time? Could you describe in more detail what your steps are that led to this issue?

Which version of the spine-unity runtime are you using (name of the unitypackage, also listed in Assets/Spine/version.txt)? If you're not using the latest available package, please be sure to update and test whether this already fixes your issue (as always, create a backup of your project first).

Which skeleton component are you using? Since your stack trace contains "MeshRenderer", I would assume that you're using either SkeletonAnimation or SkeletonMecanim. Nevertheless since you mentioned "window of the interface", for UI elements you should be using SkeletonGraphic instead.

FSL

Harald

Sorry, my description is not accurate enough to make you confused. After that I made some tests on this problem, and get some points as follows:

This problem occurs when repeatedly creating and destroying UI type spine resources (Just like opening an interface with spine resources, then close and destroy it, and then reopen it. Repeat this for several times. Also, waiting
for a while after first loading and destroying the resources, and then open this UIWindow again, it also happens).

The version of spine unity runtime being used is spine unity 3.8-2020-06-18. unitypackage;

I use the SkeletonAnimation component for one resource and the SkeletonGraphic component for the other resource;

When I tried to comment out the code and make this interface load only one resources, I found that the SkeletonGraphic component's resources also encountered this issue when loaded and destroyed separately; But SkeletonAnimation won't.

Harald

While I still don't understand what you mean by "UI type spine resources" and what you mean by "an interface", the spine-unity version you are using is 3.8 2020-06-18 which is not the latest 3.8 package available, which is 2021-11-10. Please always upgrade the spine-unity package first before reporting any issues.

The latest 3.8 unitypackage is available for download here as usual:
https://esotericsoftware.com/spine-unity-download#Older-Versions

Since Spine 3.8 is already very old, I'm afraid to say that there will be no updates published for the 3.8 and 4.0 spine-unity runtimes any more, so if the problem persists after updating the 3.8 runtime, please have a try whether the same problem still occurs with the latest 4.1 spine-unity runtime. Then we can work on a bugfix and share the code with you, so that you can integrate it in your code as well.