GLTFLoader Memory Usage Issue

Based on the information provided, you're experiencing a significant memory consumption issue when loading a very small glTF model (869B cube) that results in over 200MB of GPU memory usage.

This issue is likely not directly related to the GLTFLoader itself, but rather to how browsers and graphics drivers handle WebGL resources. There are several potential causes for this behavior:

1. Texture and Buffer Allocation: WebGL might be allocating memory in larger chunks than needed, especially for small models.

2. Mipmapping: If the model has textures, automatic mipmapping could be generating multiple resolution versions of each texture.

3. Shader Compilation: Each material in Three.js requires shader compilation, which can consume additional memory.

4. Browser's WebGL Implementation: Different browsers handle WebGL memory differently, and some may have higher overhead.

5. Debug Information: In development environments, browsers might store additional debug information for WebGL contexts.

To potentially reduce memory usage, you could try:

• Disposing of unused resources properly
• Using shared materials when possible
• Optimizing textures (size, format)
• Using the DRACOLoader for compression if you're loading multiple models

If you need to work with many models in a memory-constrained environment, you might want to implement a resource management system that loads and unloads models as needed.

The issue appears to be consistent across browsers and platforms, suggesting it might be related to how WebGL fundamentally allocates resources rather than a specific Three.js implementation detail.