Non-paged pool memory leak (UCOD tag grows continuously when VS Code is running)

Environment

VS Code Version: 1.127.0
OS Version: Windows 10 Pro 1909 (Build 18363.592)
Description
After launching VS Code, the system's non-paged pool memory begins to increase continuously at a rate of about 2 MB per second.
Monitoring with PoolMon shows that the kernel pool tag UCOD grows consistently while VS Code is running.
The leak continues even when all extensions are disabled, and VS Code is opened with a large project (AOSP SDK).

Closing VS Code immediately stops the non-paged pool growth.

PoolMon Information

Tag: UCOD
Type: Non-paged pool
UCOD allocations (Allocs - Frees) increase over time
Screenshot attached below (PoolMon showing UCOD growth)
(attach your screenshot here)

Steps to Reproduce

Disable all VS Code extensions
Open VS Code
Open the AOSP SDK project
Open an elevated PowerShell window and run poolmon -b
Monitor the UCOD tag
Non-paged pool usage increases steadily at ~2 MB/s
Closing VS Code stops the UCOD growth immediately
Expected Behavior
VS Code should not cause continuous kernel non-paged pool allocations.

Actual Behavior
The UCOD kernel pool tag continuously grows as long as VS Code is running, causing:

Increased non-paged pool usage
System memory pressure
Potential instability or slowdown over long sessions
Additional Information

All extensions are disabled
The project opened is a very large codebase (AOSP SDK)
Issue happens consistently after several tests
Appears related to Electron or underlying system calls that allocate UCOD-tagged kernel memory