Texture sizes are 10x bigger in iOS builds from 6000.0.24f1 vs 2023.2.20f1

[ROBYER1]

Describe the bug 💬

This project exported and ran fine in Unity 2023.2.20f1 on iOS running on an iPad Pro - when I updated it to Unity 6000.0.23f1 and also 6000.0.24f1, I noticed the allocated size of textures in the build in the memory profiler are nearly 10x the size of the textures in the build from Unity 2023.2.20f1.

I have cross checked this doesn't happen with textures linked to obj, dae or fbx files imported into Unity and this only is happening with .glb files.

I have a small repro project here using the DamagedHelmet.glb example file from the Khronos GLTF sample models repo where I opened it in Unity 2023.2.20f1, built to test then opened it in Unity 6000.0.24f1 without changing anything built and tested it to cross reference this - See size differences of the DamagedHelmet.glb textures.

Unity 2023.2.20f1

Unity 6000.0.24f1 LTS

Steps to reproduce 🔢

1. Download the attached project from the repro files below, open in Unity 2023.2.20f1 as build target iOS on Silicon Mac Editor (not intel)
2. On Models > DamagedHelmet, ensure UnityGLTF is the importer for the model
3. Build and run it on iOS to a device like an ipad Pro as development build with auto link profiler on
4. In Memory Profiler, grab a memory snapshot of the running build
5. Repeat the steps above with Unity 6000.0.24f1 as build target iOS on Silicon Mac Editor (not intel)
6. Compare the memory snapshots

Files to reproduce the issue ♻

MemoryRepro.zip

Editor Version 🎲

6000.0

Render Pipeline and version

URP 16.0.6

UnityGLTF Version

2.14.0 & 2.14.1 tested

Operating System 👩‍💻

macOS, iOS

When does this problem happen?

• Editor Import
• Runtime Import
• Editor Export
• Runtime Export

Additional Info 📜

No response

Validations 🩹

• I have searched existing issues: no issue already exist that reports the same problem.
• I follow the Code of Conduct
• I provided a minimal reproducible example, including files when necessary.

[hybridherbst]

Thanks for the detailled information! Just to be clear, is this the bug you also sent to Unity about this change of behaviour? Could you reference the issue number here?

[ROBYER1]

It is the same issue I sent to Unity although I sent them a larger bug repro project than the one linked here, I will follow up my bug report with the same zip linked here if required.

The Unity issue is
IN-87705

[ROBYER1]

I haven't managed to reproduce this on Windows build platform target so I would assume this is specific to iOS for now.