AssetManager and OpenGL Texture Cache Interaction After Context Loss

Direct answer

No—AssetManager should not automatically detect OpenGL context loss and reload textures by default. An optional, default-off invalidation hook is defensible, but explicit developer control must remain the primary contract.

Confirmed facts

AssetManager is a CPU-side asset cache. It manages file handles, reference counts, dependency graphs, and loader instances. It does not own the GL context, and in stock libgdx it has no callback that tells it a texture name has become invalid. After context loss on Android, the CPU-side TextureData or Pixmap remains reachable, so AssetManager.get() can return the same Texture object while its underlying GL texture ID is stale.

Likely explanation

When the activity is backgrounded and the GL surface is destroyed, the GPU-side texture names are lost. Because AssetManager still holds a live reference to the Texture, the manager believes the asset is loaded. Rendering then samples an invalid name, producing a black texture, a GL error, or undefined content. AssetManager cannot fix this on its own because it must not call GL functions from a background thread or from update().

Trade-offs

• Automatic reload reduces Android boilerplate but risks frame stalls, duplicate uploads, memory spikes, and reentrancy if triggered from the GL thread. It can also break projects that manually dispose and reload assets or that use custom AssetLoader implementations caching GL objects.
• Explicit control lets the app batch reloads during resume(), prioritize critical textures, and report progress through the normal update() loop. This matches the documented Android lifecycle responsibility.

How an opt-in feature should coexist

1. Keep the flag default-off and Android-scoped; desktop context loss is rare enough that a cross-platform auto-reload adds risk without proportional benefit.
2. Expose invalidation events or a reload() method on AssetManager. Let the Android backend or a renderer wrapper decide when the GL context is usable again.
3. When the app opts in, skip disposed or unloaded assets, queue reload work, and process it through the existing update() loop so progress and error handling stay consistent.
4. Do not change get(), isLoaded(), or unload() semantics. Existing projects that manually dispose and reload must continue to work unchanged.

Practical verification

Before implementing, confirm the behavior on your exact libgdx version and backend. A minimal check:

// Pseudocode for verification only
Texture tex = assetManager.get("img.png", Texture.class);
int handleBefore = tex.getTextureObjectHandle();
// Background the app, enable "Don't keep activities", then resume
int handleAfter = tex.getTextureObjectHandle();
// Compare handles and render a frame

Enable the Android developer option Don't keep activities, background and foreground the app, and capture logcat for GL errors alongside AssetManager progress. If you use a custom AssetLoader that caches GL objects separately, a global opt-in flag is the wrong tool; you need loader-specific invalidation hooks instead.

One missing detail

Do your custom loaders cache GL objects outside the standard Texture/TextureData path? If yes, the recommendation shifts from a global AssetManager flag to per-loader invalidation callbacks.