Summary
This issue seems to be isolated to me, as I know many verse programmers who have not had this issue. Perhaps more interestingly, I am able to reproduce this on my brand-new laptop, which I got 3 weeks ago. Even reinstalling the URC extension does not seem to resolve this issue.
With the Unreal Revision Control (VS Code Extension) enabled, upon booting up everything seems normal. As soon as I start coding, VSCode’s extensions crash and reboot.
Upon investigating using Windows Event Viewer, VSCode Logs, and Task Manager, I have discovered that every time I initially start coding with URC enabled, my VSCode’s extension host Committed Memory jumps higher and higher until my limit causes a crash.
It is worth noting that with URC disabled I get a stable, expected 904,000K commit size, and with it enabled I see an idle at 25,000,000K (22,000,000K on my laptop). It appears to remain stable at this unusually high number until I type, at which point it starts hiking at about 3,000,000K/s until it hits the limit and crashes. I have tested this as the only extension enabled (alongside Verse) and verified it happens only with this extension on (Couldn’t replicate with only Verse).
I was tempted to say that this was some sort of project level corruption, but it follows me on any project I work on and is rather annoying as I rely on being able to see those green, blue and red lines more than I’d like to admit to remember what I’ve touched in a session.
Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
Unreal Revision Control
Steps to Reproduce
Install UEFN/Fortnite
Open VSCode in a project
Wait for extensions to load (ensure URC is enabled)
Use task manager to view Commit size (if unusually high, you will be able to replicate)
Start typing in VSCode in any verse file in your workspace (no saving needing)
Immediately notice spiking of Commit size in task manager, followed by a crash of VSCode’s extension host.
Expected Result
Extension works and integrates with project well and successfully, without an unusual memory commit size.
Observed Result
For my case, exponential commit size allocation until crash
Platform(s)
Windows 11 (VS Code)
Additional Notes
EPIC: I can provide screenshots, log files, setups, and more if they would be helpful, but would prefer to do so in a non-public manner. Please contact me if you would like this information.