Before running the app, CachedWebRootFileProvider.PrimeCache forces cache on all files inside wwwroot. Many of these files are non-minified and never get served in production (bootstrap.css, jquery.js), needlessly taking up hundreds of kilobytes in memory.
The cache itself didn't like that and didn't want to cooperate until it was forced to by setting CompactOnMemoryPressure = false. Maybe this wouldn't even be necessary if it only cached things that are actually needed? Also, if this is a problem for dev environment, caching could only be enabled in production.
Before running the app, CachedWebRootFileProvider.PrimeCache forces cache on all files inside wwwroot. Many of these files are non-minified and never get served in production (bootstrap.css, jquery.js), needlessly taking up hundreds of kilobytes in memory.
The cache itself didn't like that and didn't want to cooperate until it was forced to by setting CompactOnMemoryPressure = false. Maybe this wouldn't even be necessary if it only cached things that are actually needed? Also, if this is a problem for dev environment, caching could only be enabled in production.