A NestJS app under load shows high memory usage. Profiling reveals many request-scoped providers are never destroyed. What is the most likely cause?
-
A
The REQUEST-scoped providers are injected into singleton-scoped providers, preventing their destruction
-
B
Request-scoped providers are always leaked in NestJS
-
C
The DI container has a memory limit configuration that is too low
-
D
Using @Injectable({ scope: Scope.REQUEST }) opts out of garbage collection