ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal: Determine if a Singleton provider that depends on a Request-scoped provider is instantiated once per application lifecycle or recreated for each incoming request, and assess the associated DI tree reconstruction overhead in high‑throughput NestJS applications. Constraint: The NestJS documentation states that injecting a Request-scoped provider into a S
When working with a large Ruby on Rails codebase in RubyMine, resident memory grows steadily over a session and is not released after closing files or running garbage collection. The goal is to determine whether this is expected caching behavior or an actual leak, and to identify which component is responsible. Three candidate contributors are documented: th
During long Maya sessions, resident memory climbs steadily and is not returned to the OS after closing a heavy scene with File > New Scene. The only eventual failure condition is a platform-dependent out-of-memory crash, so there is no error string to anchor diagnosis. The unresolved question is how to classify this growth before it reaches that point. Tw
In web3.js v1.5.x the WebSocketProvider keeps event listeners after an unsubscribe call, leading to incremental memory growth when newBlockHeaders subscriptions are created repeatedly. The documented fix is to call subscription.unsubscribe() followed by provider.disconnect() before process exit, which releases listeners and closes the socket. However, the de
Evaluating Rancher memory leak detection options Goal: Choose between Rancher’s native /metrics endpoint and an external Prometheus stack from the monitoring catalog to identify upward memory trends in the server or agent components. Constraint: The Rancher HA setup recommends a metrics scrape interval of no more than 15 seconds to limit overhead, yet the ag
GlobalScope marked @DelicateCoroutinesApi Starting with kotlinx.coroutines 1.3.x, the library annotates GlobalScope as @DelicateCoroutinesApi , signalling that fire‑and‑forget launches are leak‑prone because they are never cancelled by a lifecycle. The documented mitigation is to use structured concurrency: create a CoroutineScope tied to a lifecycle and can
When a DOS program uses INT 21h AH=48h to allocate a conventional memory block and then terminates abnormally (e.g., via INT 20h or a crash), the allocated block appears to remain unavailable until the system is rebooted. The DOS memory manager does not keep per‑program allocation records, and there is no documented API to query or release memory that was al
Classic Visual Basic 6 (pre-.NET) and VBA destroy a COM object only when its reference count reaches zero. A parent class and child class that hold references to each other therefore never terminate: Class_Terminate never fires, and any cleanup code placed there silently never runs. Two documented ways to break such a cycle exist: Explicit teardown — a Clean
When an application repeatedly initializes and destroys DataTables instances, the documented destroy() method is the supported teardown path. The goal is to determine how completely destroy() releases internal event handlers and DOM node references, and what diagnostic criteria separate a DataTables-side retention issue from references held by surrounding ap
rails
rubymine
maya
web3js
rancher
prometheus
kotlin
msdos
visualbasic
datatables
jquery
nestjs