Extension Host crashed: Activation sequence priority during automatic restarts

Extension Host Recovery Behavior

Visual Studio Code utilizes a separate process for the Extension Host to ensure UI stability. When this process terminates unexpectedly, the editor triggers an automatic restart mechanism to restore extension functionality and displays the notification "Extension Host crashed".

While the memento API allows extensions to persist state across these failures, there is uncertainty regarding the activation order during a recovery cycle compared to a standard cold start. Specifically, it is unclear if the system prioritizes extensions that were active at the time of the crash or if it reverts to the standard activation event sequence.

Given these constraints, what is the documented priority logic for extension activation during an automatic host restart? Does the recovery process differentiate between active and dormant extensions to optimize restoration speed?