Hey there! We’ve identified the issue and we’ll have a fix for it our next release. There’s a call to Resources.LoadAll("") in PolySpatial code that results in everything from Resources getting loaded into memory. It’s part of material conversion so there’s no way to disable or avoid that code path being hit.
I don’t have a precise timeline for when we can deliver the next release, but unfortunately there’s nothing you can do about this on your end aside from reducing the amount of data in Resources. It might be worth trying addressables. The documentation is referring to some specific PolySpatial issues related to loading materials and some other asset types, but addressables as a whole should still work. It may be possible to pick and choose what goes into Resources vs. addressables if you find that some of the addressable assets still work.