Retired generation remains alive

A retired module's collectible assembly load context is still alive after two natural full garbage collections. The active generation can keep running, but the retired generation's memory remains retained. The loader reports an L4 restart request to reclaim it.

#Common causes

• A static event subscription or long-lived cache outside the retired generation still references its objects, delegates or types.

#Fixes

• Remove long-lived references to module generations and release subscriptions or caches when retiring them.

• Restart the play process from a snapshot to reclaim leaked generations; do not add gameplay GC.Collect() calls as a workaround.

• Code: ARA0927

• Constant: script::GENERATION_LEAKED

• Reported by: ara-script, Ara.Host