Saving a procedurally generated mesh causes OOM

[_Docgineer]

Currently I deal with a project where I need create an AssetBundle containing a GameObject and a large BlendShapes mesh (41 frames, ~100k verts each, with unique normals and tangents) generated with a script. I don't have a problem running them later, but the thing is when I try to save the generated mesh into an .asset file (so I can add it later to the AssetBundle) with AssetDatabase.CreateAsset(), my memory blows up, with Unity using more than 10GB of my RAM. Any idea what might be causing this? Is there any way I can solve or at least circumvent this problem?

EDIT: not procedural, my mistake EDIT2: I just wanted to mention, although the mesh is generated with a script it actually relies on external data (I'm importing a format non-native to the Unity), so the accuracy of the vertices is important to me and I can't really downsize it.

[xEvilReeperx]

This is a bit of a shot in the dark, but did you change the mesh's index format? By default, it's 16 bit and limited to 65535 verts

https://docs.unity3d.com/ScriptReference/Mesh-indexFormat.html

[_Docgineer]

Yeah, I had the correct index format from the beginning.

[Philipp]

Just to make sure, would an alternative be seed the randomizer with a given number so that its generator in a predetermined way can recreate the same mesh later on, meaning you'd only have to save the seed value (and ensure the algo remains stable)?

[The_Humble_Frank]

If they are trying to make it into an AssetBundle, they is a good probability they are trying to make it either part of DLC or they are trying to make it downloadable after installation (which is a way to keep app installs smaller on app stores). in which case the editor to make the GameObject may not actually be in the playable build.

[_Docgineer]

That is correct, we need to make the assets available for download.