Diagnostic code · ARA2021
Reload fell back to L3
An edit that could have been patched in place (L1/L2, tens of milliseconds) was applied as a full module swap (L3, a few hundred milliseconds) instead. The message names the reason the compile server or the runtime gave.
Common causes
- A changed method contains a lambda, local function or LINQ query (EnC deltas for closures crashed the runtime in S2, so they always take L3).
- A declaration changed: a signature, a struct field, an attribute or a virtual member.
- A constructor, field initializer, iterator or
asyncmethod changed. - The module was cold (built optimized); its first edit makes it hot.
- A debugger is attached, so the runtime refuses EnC deltas.
- A module this one references changed its public surface.
Fixes
Keep hot-path edits to plain method bodies; move lambdas into named methods when you iterate on them.
Detach the debugger while iterating.
Expect one L3 per module after a cold start; later body edits take L1.
Code:
ARA2021Constant:
RELOAD_ESCALATEDReported by: ara-script