Which strategy prevents memory spikes during high-volume AssetManager loading?

The libGDX AssetManager utilizes an asynchronous queue to load resources like textures and shaders without blocking the render thread. While update() handles the progression of this queue, there is a potential for significant memory spikes when a large volume of assets is queued simultaneously before they are uploaded to the GPU and the CPU-side buffers are cleared.

In scenarios requiring the loading of hundreds of high-resolution assets, simply calling load() for all items may exceed available heap space before the manager can process the queue efficiently.

• Does the AssetManager support a native way to throttle the number of concurrent loading tasks?
• What is the recommended approach to batch asset loading to maintain a stable memory footprint?