Summary
The Unreal Revision Control VS Code extension repeatedly hard-crashes the VS Code shared extension host (UtilityProcess) roughly every 2–3 minutes while working in a Verse project that is connected to Unreal Revision Control (workspace contains a .lore folder). Because the crash is a native fail-fast in the extension’s own lorelib DLL, it takes down the entire extension host process — so every other extension sharing it (Verse language support, GitHub Copilot, Anthropic Claude Code, etc.) dies at the same time. Any in-progress work in those extensions is lost. This makes the editor effectively unusable for long-running tasks.
Faulting module
epicgames.urc-vscode-1.0.54782332\node_modules@lore-vcs\sdk-amd64-unknown-windows\lorelib-amd64-unknown-windows.dll
Crash signature (Windows Error Reporting, BEX64):
Faulting application: Code.exe (1.127.0.0)
Faulting module: lorelib-amd64-unknown-windows.dll
Exception code: 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN / __fastfail)
Fault offset: 0x00000000015DB4E1
VS Code main-process log at time of crash:
Extension host with pid exited with code: 3221226505, signal: unknown.
[UtilityProcess type: extensionHost]: crashed with code -1073740791 and reason ‘crashed’
(3221226505 = -1073740791 = 0xC0000409 — a native abort, not a JavaScript exception; nothing is logged in exthost.log because the process is terminated instantly.)
Related activity in the extension logs
Crashes correlate with the extension’s remote-change monitoring / teardown path. During shutdown the following errors appear repeatedly:
Error: Shutting down, not executing new commands
at UrcCliV2Provider.callUrcLib (…\urcProvider\urcCliV2Provider.js)
at UrcCliV2Provider.stopRemoteChangeMonitoring (…\urcProvider\urcCliV2Provider.js)
at UrcCliV2Provider.dispose (…\urcProvider\urcProviderBase.js)
at UrcSourceControl.dispose (…\sourceControlProvider\urcSourceControl.js)
This suggests the native lorelib call (possibly during stopRemoteChangeMonitoring / remote-change polling) hits an unrecoverable condition and fail-fasts the process rather than returning an error.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Other
Steps to Reproduce
1.Open a UEFN project that is connected to Unreal Revision Control (workspace contains a .lore folder) in VS Code with the Unreal Revision Control extension enabled.
2.Edit Verse files and leave the editor running for a few minutes (so remote-change monitoring runs).
3.Within ~2–3 minutes the extension host crashes (0xC0000409 in lorelib). All extensions restart; any in-progress operation is lost. This repeats indefinitely.
Expected Result
lorelib errors should be handled gracefully (returned as recoverable errors) instead of fail-fasting and crashing the shared VS Code extension host.
Impact
Extension host crash-loops every few minutes, making the editor unusable for sustained work.
Because it’s a native crash of the shared host, it also crashes unrelated extensions (Verse, Copilot, Claude Code) — not just Unreal Revision Control.
Observed Result
Disabling the Unreal Revision Control extension in VS Code stops the crashes entirely (revision control can still be managed from the UEFN editor). This confirms the crash originates in this extension’s native lorelib DLL.
Platform(s)
PC