ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Background jobs created with Start-Job remain in the session until Remove-Job is called, even after completion. This behavior can lead to elevated memory consumption in long‑running scripts. In PowerShell 7.2 a known bug caused job objects to stay in memory after Remove-Job , resulting in a measurable leak; the issue was fixed in 7.3 and later releases. Howe
Goal Determine whether core-js DOM collection polyfills exhibit memory leak patterns that persist across versions, particularly when used in long-running browser applications. Constraints The investigation must focus on documented behavior rather than unverified reports. Memory leak patterns may differ between core-js 2.x and 3.x branches due to architectura
When injecting Request-scoped beans into long-lived Singleton beans, Spring typically utilizes a ScopedTargetProxy to manage the lifecycle mismatch. While this allows the singleton to reference the proxy, memory leaks can occur if the underlying request context is not properly cleared after the HTTP request completes. In high-concurrency environments using c
Node.js offers two documented mechanisms for tracking async context: the low-level async_hooks API and the higher-level AsyncLocalStorage. Both rely on the same async resource model, but they differ sharply in memory behavior. async_hooks exposes granular lifecycle events, enabling custom propagation and deep diagnostics, but it is marked experimental (Stabi
Titanium SDK 9.3+ AndroidX Compatibility The 9.2.0 release resolved a documented memory leak in Ti.UI.WebView on Android by cleaning up native Chromium resources during the view’s destroy lifecycle. While this fix stabilizes heap usage, a new configuration boundary emerged with SDK 9.3.0: the build process defaults to AndroidX libraries, yet the SDK still sh
Problem Context When Sourcetree performs a git fetch on repositories larger than roughly 2 GB, the application log records java.lang.OutOfMemoryError and the process terminates. The embedded JGit implementation retains RevWalk and ObjectLoader instances, leading to heap exhaustion. Implemented Fix Atlassian released version 3.4.10 (March 2022) that raises th
Goal: determine whether Bun's zero‑copy HTTP server reuses buffers in a way that can cause memory leaks under sustained high concurrency. Constraints: use the latest stable Bun release, run a simple Bun.serve() endpoint that echoes request bodies, no custom buffer pools, on a Linux system with default TCP stack. Monitor RSS via top or htop while generating t
Goal Determine whether Photoshop’s undo stack causes a memory leak when working with large canvases and extensive undo history. Constraints 64‑bit Photoshop on Windows 11, document size > 50 MB, RAM allocated set to 8 GB in Preferences > Performance. The test involves repeated undo/redo cycles and monitoring system memory via Task Manager. Unresolved Q
In p5.js 1.5.0 the p5.Sound library added a patch that calls stop() and disconnect() on all AudioBufferSourceNode objects before freeing them, which eliminates the memory leak that appeared in 1.4.0. However, the library still keeps the global AudioContext alive, even after a sketch stops or is removed. When using instance mode, multiple sketches can be crea
corejs
spring
nodejs
titaniumsdk
bun
photoshop
p5js
powershell