High memory usage with SDK imported

[ko-tengu]

SDK version

0.0.7

Unity version

2022.3.22f1

Resonite version

2026.4.1.11

I tested the issue without mods.

Yes

What happened?

The SDK causes the Unity Editor to use a rather extreme amount of ram even sitting idle.

What were you expecting?

To not use 14gb of ram for a project with one avatar and one shader imported.

Logs

Editor.log

[Frooxius]

Is this before even doing any kind of conversion?

This is very strange, since the idle SDK should not even be running any code. How do you know this RAM usage came from the SDK and not the project itself (e.g. lots of assets in the scene)?

[ko-tengu]

This is me launching the scene and proceeding to do nothing, the active scene (and all assets in the project) are about 50mb of the haolan avatar I've attached to previous errors.

In testing I've also imported the SDK into a completely empty project and it causes the ram usage to jump from about 500mb for an empty unity project to about 1.5gb after importing the Resonite SDK.

[BitCrack]

I have actually experienced this myself recently when I was trying to import an avatar, when importing the SDK the editor ran out of memory.

To isolate the issue I created an empty project with only the VRChat SDK and Poiyomi.
After this new project opened I imported Resonite SDK and during the process Unity ran out of memory.
I do have 16 GBs of RAM which I think should be fine for this?
Below are times for different parts of the video I recorded and the contents of the message from the OOM crash.

0:00-4:25 - Setting up the fresh project
4:25-5:58 - Importing Unity SDK
5:58 - OOM crash

Could not allocate memory: System out of memory!
Trying to allocate: 2066402854B with 16 alignment. MemoryLabel: DynamicArray
Allocation happened at: Line:80 in C:\build\output\unity\unity\Runtime\Core\Containers\Vector.h
Memory overview

[ ALLOC_TEMP_TLS ] used: 0B | peak: 0B | reserved: 58032128B 
[ ALLOC_MEMORYPROFILER ] used: 914320B | peak: 917624B | reserved: 2097152B 
[ ALLOC_DEFAULT ] used: 33668664352B | peak: 0B | reserved: 33714249728B 
[ ALLOC_TEMP_JOB_1_FRAME ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_JOB_2_FRAMES ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_JOB_4_FRAMES (JobTemp) ] used: 0B | peak: 0B | reserved: 165675008B 
[ ALLOC_TEMP_JOB_ASYNC (Background) ] used: 87B | peak: 0B | reserved: 5242880B 
[ ALLOC_GFX ] used: 63048968B | peak: 0B | reserved: 83894272B 
[ ALLOC_CACHEOBJECTS ] used: 103961836B | peak: 0B | reserved: 166133760B 
[ ALLOC_TYPETREE ] used: 752824B | peak: 0B | reserved: 16777216B 
[ ALLOC_PROFILER ] used: 654136B | peak: 670224B | reserved: 16777216B 
[ ALLOC_PROFILER_EDITOR ] used: 0B | peak: 0B | reserved: 0B 

UnityEditor.AssetDatabase:FindAssets (string)
Poi.Tools.ThirdPartyIncluder:GetAllThirdPartyIncluders () (at Assets/_PoiyomiShaders/Scripts/poi-tools/Editor/Export Stuff/ThirdPartyIncluder.cs:37)
Poi.Tools.ThirdPartyIncluder:get_thirdPartyIncluders () (at Assets/_PoiyomiShaders/Scripts/poi-tools/Editor/Export Stuff/ThirdPartyIncluder.cs:18)
Poi.Tools.ThirdPartyIncluder:DoAllThirdPartyIncluders () (at Assets/_PoiyomiShaders/Scripts/poi-tools/Editor/Export Stuff/ThirdPartyIncluder.cs:96)
UnityEditor.EditorApplication:Internal_CallDelayFunctions ()

2026-04-05.17-45-36.mp4

I have also tried importing the Unity SDK with the VRC SDK but without Poiyomi and during importing Unity spiked at 10 GBs of usage and after importing settled at 6.8 GBs but in the end it did manage to import.

And on a completely empty project:

• Idle before importing - 640MB
• Max when importing - 6GB
• Idle after importing - 1.5GB

[Frooxius]

@ko-tengu So if I understand this correctly, you simply opened a scene with the avatar, but did not use the SDK at all and the usage was at ~14 GB?

Was the Resonite SDK window open? Did you connect to session? Or literally just nothing?

If the SDK wasn't even opened in the scene, I don't think the usage would be coming out of this. It might help to use the Unity tools to analyze what's using memory potentially, because 14 GB seems very abnormal, especially if the SDK's code isn't even invoked at all.

[ko-tengu]

I opened the project with this scene open and the ResoniteSDK pane opened, but not connected to a Resonite session (or even have Resonite open to attempt to connect to)

[Frooxius]

Can you replicate this repeatedly?

I tried the same steps, but I can't replicate it, the memory usage is just ~850 MB for me when I do that.

I honestly don't know if the high usage is really coming from the SDK itself - I can't even think of a potential technical reason why it would use 14 GB of RAM when the code isn't even running.

[Baplar]

I am also consistently getting crazy amounts of RAM usage during the initial import of the SDK (we’re talking dozens of GB, sometimes it’s enough to completely saturate my 32GB of RAM + 32GB of swap, and crashing to desktop!).
But if and when the import completes, the RAM usage falls back down to something manageable (about a GB).

However, I am on Linux, and as we know, Unity on Linux is not renown for its quality or stability...
But even though the magnitude of the problem is multiplied drastically for me, the symptoms are similar in nature, so it might be the same underlying issue?

[Frooxius]

Is this specifically when you import the SDK in into Unity?

[ko-tengu]

For my uses, it's just every single launch. The SDK just consistently uses up an additional 1-13GB compared to a project without it.

How much extra is pretty variable, but it's consistently much higher than a project without the SDK imported.

[BitCrack]

I've been trying to get to the root of my issue (OOM when importing) and after some trial and error I noticed that I still crashed when removing everything except the Plugins directory. And as I expected by then, removing Resonite.UnitySDK.Bindings.* let me finally load the Unity editor normally, which makes me think the issue is related to that file/bindings themselves. But it doesn't look like it should be executing anything and there's not enough code for it to cause additional 9-10 GBs (in my case) of RAM usage when importing?

[Frooxius]

Hmm... I wonder if it's Unity doing its processing on the assemblies somehow.

I've ran a test of importing the UnityPackage to the project and it does spike near the end of the import process, but then goes back down:

I can look if there's any options to skip some processing in Unity that might cause this, but since this is something Unity-side, before any actual code runs, this is a bit tricky issue resolve.

[ko-tengu]

In the interest in trying to solve this, along with my test project being entirely free to distribute assets, attached is my entire unity project folder, ready to be imported through unity hub. I'm also attaching the log of the most recent time launching it, where it immediately ballooned to 16gb of RAM even though I've done no changes to this project in a week.

https://1drv.ms/u/c/fbde950f0d103ab4/IQAFqiA2elE9Q7gP3GKZcw9yAW__l7o5nPl0yzBSdL0E-Y0?e=o2K8Ot (671mb download; 5.3gb extracted)

Editor.log