Dynamic library file size | Official Unity Discord | Page 1

green charm Jul 14, 2025, 10:42 AM

#

Hello there.
Does anyone know a good way to figure out why the primary dynamic library file of a build is too large?

Context: I currently have a situation in our game where the PS5 build has a very large Il2cppUserAssemblies.prx, which afaik is the primary dynamic libary file used by the PS5 build. Without any stripping or compression the file can have a size of up to 2GB in a debug config, which stops the build from running on PS5 afaik due to bandwith limits.

Now, afaik the corresponding dynamic library files on PC would be the GameAssemblies.pdb & GameAssemblies.dll. Given the same project, I've noticed that those files are also quite large, similar to the one on PS5.

My question would be how could I figure out what's causing the file to be come so large? (Even in release mode it's still roughly at 1.8GB)

chrome mountain Jul 14, 2025, 1:37 PM

#

green charm Hello there. Does anyone know a good way to figure out why the primary dynamic l...

You should ask in the platform specific forum. Usually, it is due to high amount of generics and/or unused package.

You could always look into the il2ccpOutput of a given build. It is in the "BackUpThisFolder_ButDontShipItWithYourGame" folder

green charm Jul 14, 2025, 1:38 PM

#

It's the same case on PC as well

chrome mountain Jul 14, 2025, 1:38 PM

#

For reference, mine is 600mb for a 4G package

#

Talking about platform is not allowed outside their respective forums

fair vapor Jul 14, 2025, 6:37 PM

#

Does anyone know a good way to figure out why the primary dynamic library file of a build is too large?
it's templates 🙂

#

there are a bunch of AOT flags you can set to reduce the amount of superfluous AOT templates that are compiled. at the very least, you have chosen the maximum assembly stripping profile so far?

#Dynamic library file size