(Remote Config) Calling ConfigManager.FetchConfigs from FixedUpdate throws "A Native Collection has not been disposed, resulting in a memory leak."

Questions & Answers
1

I’ve got this Error In unity 3D after I started using Remote Config:

A Native Collection has not been disposed, resulting in a memory leak. Allocated from:

Unity.Collections.NativeArray`1:.ctor(Byte, Allocator)

UnityEngine.Networking.UploadHandlerRaw:.ctor(Byte)

Unity.RemoteConfig.ConfigManagerImpl:DoRequest(String) (at Library\PackageCache\com.unity.remote-config-runtime@1.0.1\Runtime\ConfigManagerImpl.cs:267)

Unity.RemoteConfig.ConfigManagerImpl:PostConfig(Object, Object) (at Library\PackageCache\com.unity.remote-config-runtime@1.0.1\Runtime\ConfigManagerImpl.cs:204)

Unity.RemoteConfig.ConfigManagerImpl:FetchConfigs(appAttributes, userAttributes) (at Library\PackageCache\com.unity.remote-config-runtime@1.0.1\Runtime\ConfigManagerImpl.cs:188)

Unity.RemoteConfig.ConfigManager:FetchConfigs(appAttributes, userAttributes) (at Library\PackageCache\com.unity.remote-config-runtime@1.0.1\Runtime\ConfigManager.cs:96)

Movement:FixedUpdate() (at Assets\scripts\Movement.cs:27)

3

_
This error says that your script Assets\scripts\Movement.cs ( at FixedUpdate) calls ConfigManager which allocates memory for networking communication and that memory wasn’t deallocated.
_
If you see this warning only once when play mode ends I would ignore it for now. It might be temporary and minor package issue.

But if you’re getting spammed with this message A LOT then to fix this you must help this ConfigManager deallocate it’s memory somehow or stop calling it.

2

you can double click the last line of the error to jump to the point in your script that caused the problem. (if you use visual studio, which i highly recommend)