# Memory Leaks A programming error in which memory that is no longer needed is not released or reclaimed, causing memory consumption to grow. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mesa 26.2.3 Released With AMD GFX1171 Support, Other Fixes DevFeed: [Mesa 26.2.3 Released With AMD GFX1171 Support, Other Fixes]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T21:18:50Z Content type: news Language: en Sources: [Phoronix]() Topics: [GPU](), [patches](), [Adreno](), [intel](), [Qualcomm](), [Firefox](), [Memory Leaks](), [Flight]() Tags: [adreno](), [amd](), [browser](), [bug](), [bug-fixes](), [desktop-linux](), [firefox](), [gpu](), [intel](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory-leak](), [open-source-graphics](), [patches](), [phoronix](), [phoronix-test-suite](), [qualcomm](), [release](), [stable](), [ubuntu-benchmarks](), [ubuntu-hardware](), [vulkan]() ### AI overview Mesa 26.2.3 is a stable bi-weekly point release containing backported bug fixes for RadeonSI, RADV, Freedreno, Turnip, Intel ANV, Asahi, NVK, and other drivers. It also adds AMD GFX1171 support. ### Source excerpt Mesa 26.2.3 is out today as the newest stable point release in this quarter's Mesa 26.2 series... ## GNOME Shotwell 33 Photo Manager Released With GTK4 Port DevFeed: [GNOME Shotwell 33 Photo Manager Released With GTK4 Port]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T10:40:50Z Content type: news Language: en Sources: [Phoronix]() Topics: [releases](), [Memory Leaks](), [bug]() Tags: [bug-fixes](), [desktop-linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory-leaks](), [news](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [release](), [releases](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui]() ### AI overview Shotwell 33 is a major release of the GNOME photo manager that ports its user interface from GTK3 to GTK4. It also adds URI opening in the viewer, reworked printing, memory-leak and potential-crash fixes, and other minor improvements. ### Source excerpt It's been quite some time since hearing any news out of the Shotwell photo manager project for GNOME, but out today is Shotwell 33 with the long-awaited GTK4 port... ## September 2026 Security Updates #1 for XCP-ng 8.3 LTS DevFeed: [September 2026 Security Updates #1 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: David Morel Published: 2026-09-08T14:07:29Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [Security](), [Vulnerabilities](), [DDoS](), [Memory Leaks]() Tags: [2026](), [cve](), [lts](), [maintenance-updates](), [memory-leak](), [release](), [security](), [september-2026](), [updates](), [vulnerabilities]() ### AI overview This article announces September 2026 security updates for XCP-ng 8.3 LTS. The fixes address vulnerabilities in Xen, oxenstored, and Tapdisk, including memory leaks, denial-of-service conditions, and out-of-bounds accesses that could allow code execution with administrator privileges in dom0. One Xen issue does not affect supported XCP-ng 8.3 LTS installations and is deferred for defense in depth. ### Source excerpt New security and maintenance updates are available for XCP-ng 8.3 LTS. This includes update to Xen, oxenstored and blktap. ## Understand memory management in Amazon RDS for PostgreSQL to avoid out of memory DevFeed: [Understand memory management in Amazon RDS for PostgreSQL to avoid out of memory]() Original publisher: [Read original article]() Author: Ankita Singh Published: 2026-08-19T22:21:10Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [PostgreSQL](), [Memory Leaks](), [Processes](), [Linux](), [Monitoring](), [Amazon Web Services](), [Availability]() Tags: [advanced-300](), [amazon-aurora](), [amazon-cloudwatch](), [amazon-rds](), [availability](), [aws](), [memory](), [monitoring](), [postgresql](), [postgresql-compatible](), [processes](), [production](), [rds-for-postgresql](), [technical-how-to]() ### AI overview A practical guide to PostgreSQL memory management on Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL. It explains how memory is allocated, how memory-intensive queries and diagnostic signals can be identified, and how to diagnose, prevent, and recover from out-of-memory events and excessive disk spilling. ### Source excerpt PostgreSQL out-of-memory (OOM) events and excessive disk spilling are among the most common production incidents on Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL. Learn how PostgreSQL allocates and consumes memory, how to identify memory-intensive queries, and how to diagnose, prevent, and recover from OOM events on both engines. ## Preparing your app for broader memory limits DevFeed: [Preparing your app for broader memory limits]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-19T19:00:00Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [App](), [Memory Leaks](), [Processes](), [cpu]() Tags: [android](), [app](), [cpu](), [memory](), [memory-leaks](), [metrics](), [monitoring](), [optimization](), [os](), [performance](), [process](), [user-experience]() ### AI overview Android 17 broadens per-app memory limits across devices. The article explains how exceeding a memory budget can cause zRAM swapping, slowdowns, and process termination, and recommends measuring and reducing an app's memory footprint. ### Source excerpt Posted by Blair Harmon, Director of Product Management, Android Platform A great user experience is central to Android's mission, and delivering on that promise requires keeping devices fast, responsive, and reliable. This is why memory optimization is more critical than ever. Across the ecosystem, new devices are maintaining or even decreasing their physical memory capacity in response to memory price increases, yet users continue to expect the same seamless, high-performance app experience. In Android 17, we introduced per-app memory limits, starting with Pixel devices, to help protect the overall user experience from applications using excess memory and causing system-wide slowdowns. Over the coming year, an increasing number of manufacturers will leverage the Android per-app memory limits across their portfolio of device RAM configurations from 4GB to 16GB+ devices. If your app exceeds these limits, it will be slowed down and may be terminated. Optimizing your app's memory footprint is essential to preventing OS throttling and maintaining a seamless user experience. In this post, we'll explore how these limits work under the hood, how to measure your memory footprint using new Android vitals metrics, and actionable steps to optimize your app or game. Understanding Memory Limits When your app exceeds its memory budget, Android takes progressive action to protect device responsiveness: zRAM Swapping: If your app reaches its allocated limit, the system forces your app's pages into zRAM (compressed RAM). While zRAM prevents immediate eviction, compressing and decompressing pages adds CPU overhead, which can result in noticeable UI jank and experience slowdowns. Process Termination: If your app continues to increase its memory usage beyond the zRAM threshold, it will be terminated by the system. To determine if your app session was impacted by these constraints in the field, you can call getDescription() within ApplicationExitInfo. If the system applied a limit, the ## Preparing your app for broader memory limits DevFeed: [Preparing your app for broader memory limits]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-19T19:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Optimization](), [User Experience](), [Memory Leaks](), [memory price increases]() Tags: [adb](), [android](), [memory-leaks](), [memory-optimization](), [optimization](), [user-experience](), [vitals]() ### AI overview This Android Developers article explains how Android 17 per-app memory limits are expanding beyond Pixel devices across a range of RAM configurations. It describes the effects of exceeding memory budgets, including zRAM swapping, CPU overhead, UI jank, throttling, and possible process termination, and outlines ways to measure and optimize app memory usage. ### Source excerpt Posted by Blair Harmon, Director of Product Management, Android Platform A great user experience is central to Android's mission, and delivering on that promise requires keeping devices fast, responsive, and reliable. This is why memory optimization is more critical than ever. Across the ecosystem, new devices are maintaining or even decreasing their physical memory capacity in response to memory price increases, yet users continue to expect the same seamless, high-performance app experience. In Android 17, we introduced per-app memory limits, starting with Pixel devices, to help protect the overall user experience from applications using excess memory and causing system-wide slowdowns. Over the coming year, an increasing number of manufacturers will leverage the Android per-app memory limits across their portfolio of device RAM configurations from 4GB to 16GB+ devices. If your app exceeds these limits, it will be slowed down and may be terminated. Optimizing your app's memory footprint is essential to preventing OS throttling and maintaining a seamless user experience. In this post, we'll explore how these limits work under the hood, how to measure your memory footprint using new Android vitals metrics, and actionable steps to optimize your app or game. Understanding Memory Limits When your app exceeds its memory budget, Android takes progressive action to protect device responsiveness: zRAM Swapping: If your app reaches its allocated limit, the system forces your app's pages into zRAM (compressed RAM). While zRAM prevents immediate eviction, compressing and decompressing pages adds CPU overhead, which can result in noticeable UI jank and experience slowdowns. Process Termination: If your app continues to increase its memory usage beyond the zRAM threshold, it will be terminated by the system. To determine if your app session was impacted by these constraints in the field, you can call getDescription() within ApplicationExitInfo. If the system applied a limit, the ## jetc.dev Newsletter Issue #325 DevFeed: [jetc.dev Newsletter Issue #325]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-08-04T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [releases](), [debug](), [Memory Leaks](), [multiplatform]() Tags: [2026](), [agents](), [compose](), [compose-multiplatform](), [debugging](), [dev](), [jetbrains](), [memory-leaks](), [multiplatform](), [published](), [remote]() ### AI overview jetc.dev Newsletter Issue #325 reviews recent Jetpack Compose releases and related artifacts, including BOM, Material3, Remote Compose, and Wear Compose updates. It also covers the five-year anniversary of Compose 1.0, composition debugging research, Compose Multiplatform content, and a reported memory leak in a Compose for Desktop design system. ### Source excerpt Compose 1.0 five-year anniversary! 1.12.0 RC! Memory leaks! Remote Compose for debugging! And... have you been through the desert with a state with no name?!? ## Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis DevFeed: [Investigating a Suspected Memory Leak in JetBrains Jewel with JVM Heap Analysis]() Original publisher: [Read original article]() Published: 2026-07-28T18:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Memory Leaks](), [Compose](), [compose-multiplatform](), [jetbrains](), [ide]() Tags: [compose](), [compose-multiplatform](), [dump](), [eclipse](), [heap](), [jetbrains](), [kotlin-multiplatform](), [memory-leak]() ### AI overview The article investigates a suspected memory leak in the JetBrains Jewel project, a Compose Multiplatform library targeting desktop applications. It explains using JVM-specific tools, including heap dumps and Eclipse Memory Analyzer Tool, to examine retained heap and identify possible memory-retention issues. ### Source excerpt A kinda-brief tale about a memory leak, a heap dump, and a one-line fix. ## July 2026 Updates #1 for XCP-ng 8.3 LTS DevFeed: [July 2026 Updates #1 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Philippe Coval Published: 2026-07-28T14:32:38Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [Security](), [Vulnerabilities](), [Memory Leaks]() Tags: [2026](), [iso](), [leak](), [lts](), [regression](), [release](), [security](), [update](), [updates]() ### AI overview This release provides security and maintenance updates for XCP-ng 8.3 LTS. It updates Xen to address multiple security advisories, fixes a XAPI regression that caused VBD leaks, and includes minor changes needed to build an updated installer ISO. ### Source excerpt This release batch contains a security update for Xen. This update also brings a fix for a XAPI regression causing VBD leaks. Other minor changes were needed to build an updated XCP-ng 8.3 LTS installer (ISO). ## Bun's migration from Zig to Rust reduced the estimated timeline from 1-2 years to 11 days DevFeed: [Bun's migration from Zig to Rust reduced the estimated timeline from 1-2 years to 11 days]() Original publisher: [Read original article]() Author: Ivan Klaric Published: 2026-07-16T16:50:20Z Content type: opinion Language: en Sources: [The Pragmatic Engineer]() Topics: [Bun](), [migration](), [Rust](), [Zig](), [Fable](), [Memory Leaks]() Tags: [bun](), [fable](), [memory-leaks](), [migration](), [rust](), [zig]() ### AI overview The article examines Bun's rewrite from Zig to Rust, focusing on memory-safety problems and the migration approach. It reports that the migration timeline was shortened from an estimated 1-2 years to 11 days, while emphasizing that thorough testing was required. ### Source excerpt To a sceptic, spending $165K to migrate Bun from Zig to Rust sounds very expensive. But to a realist, shortening a 1-2 year migration down to 11 days opens amazing new opportunities for devs. However, a thoroughly-tested project is required to pull it off. ## Android Studio Quail 2 is Stable: Multi-task with the Android Studio AI agent DevFeed: [Android Studio Quail 2 is Stable: Multi-task with the Android Studio AI agent]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-14T11:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Android Studio](), [AI Agent](), [Memory Leaks](), [debug]() Tags: [agentic](), [ai-agent](), [android-studio](), [memory-leak](), [profiling]() ### AI overview Android Studio Quail 2 is presented as a stable release with parallel Agent Mode chats, concurrent agentic workflows, native LeakCanary integration in the Profiler, and Agent Mode integration with App Quality Insights for crash analysis. ### Source excerpt Posted by Amman Asfaw, Product Manager, Android Studio Android Studio Quail 2 is now stable and ready for you to use in production, bringing a shift to your IDE with concurrent agentic workflows, natively integrated memory leak profiling, and context-aware crash remediation. Whether you are performing a sweeping architectural overhaul, tracing a memory leak, or resolving a critical production crash, Android Studio keeps you anchored in your workspace by reducing manual friction. Here's a deep dive into what's new: Multi-tasking with parallel chats In Android Studio Quail 2, we've been hard at work redesigning Agent Mode from the ground up. This new architecture provides better performance, offers more flexibility for decomposing complex tasks, and improves the suite of internal tools the agent uses to do its work. In addition to these behind-the-scenes improvements, these changes also allow you to converse across multiple agent chats simultaneously. Waiting for the Android Studio agent to finish a task before you can ask another question or initiate a separate task in Agent Mode is a bottleneck of the past. You can multi-task seamlessly: kick off a UI refactor in one tab, fix a ProGuard rule in a second, and generate documentation in a third. You can also change which models the agent uses from chat to chat based on the requests you have. Take a look at Android Bench for an analysis of how LLMs perform Android development tasks. How to use: Click the "+" icon to start a new parallel conversation, and use the History icon to navigate between active tasks. Alternatively, select File > New > New Agent Tab to open a conversation in a dedicated tab. Note: Worktree support is currently unavailable. Exercise caution when running concurrent chats that modify the same project files, which can potentially lead to editor conflicts. Run multiple agent tasks in parallel with different models of your choice. Use the History icon to navigate between active tasks. Memory leak detec ## v20.2.2 Tentacle released DevFeed: [v20.2.2 Tentacle released]() Original publisher: [Read original article]() Author: Yuri Weinstein, Patrick Donnelly Published: 2026-06-16T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [bug](), [Vulnerabilities](), [Memory Leaks](), [Encryption](), [configuration](), [IO]() Tags: [2026](), [aio](), [blog-post](), [bug](), [ceph](), [configuration](), [en-article](), [en-blog-post](), [encryption](), [io](), [memory-leaks](), [rados](), [release](), [rgw](), [storage](), [tentacle](), [ui](), [update](), [vulnerabilities]() ### AI overview Ceph v20.2.2 Tentacle is a minor release that adds Rocky 10 package-install support and recommends updating. It fixes issues across MDS, OSD, RGW, RADOS libraries, watch/notify operations, asynchronous utilities, and the dashboard, including security vulnerabilities, memory leaks, encrypted-object lifecycle problems, and UI and configuration improvements. ### Source excerpt This is the second minor release in the Tentacle series. We recommend that all users update to this release. Release Date ¶ June 16, 2026 Notable Changes ¶ Rocky 10 package-based installs are now supported starting with v20.2.2. Please see the supported platforms for current and planned support in Ceph. MDS (Metadata Server) ¶ Segmentation fault fixed due to incorrect queueing of request retries. OSD (Object Storage Daemon) ¶ PGLog Missed List: Fixed a bug to ensure the correct version is attached to the missing list when ignoring log entries. Data Integrity Asserts: Added assertions to explicitly catch potential corruption in the OSD missing list. RGW (RADOS Gateway) ¶ Lifecycle Management: Fixed lifecycle transition issues affecting encrypted multipart objects. REST & Query Handling: RESTArgs::get_string() now properly URL-decodes incoming query parameters. RADOS / librados / neorados ¶ Linger Operations: Rewrote safety checks to eliminate use-after-free vulnerabilities and LingerOp memory leaks when an unwatch operation returns ENOTCONN. Replaced the flawed is_valid_watch() check with a safe linger_by_cookie() lookup which safely manages LingerOp references using intrusive_ptr. Ensured librados linger callbacks hold a persistent reference to LingerOp to protect against races with simultaneous linger_cancel() requests. Configured librados::IoCtxImpl::aio_unwatch() to asynchronously deliver ENOTCONN to AioCompletion instead of returning the error directly. Watch/Notify: Fixed neorados notification queue bounds enforcement so that an overflow marker is only appended on the first message exceeding capacity, rather than duplicating it on every subsequent message. Prevented double-cleanup triggers in watch/notify operations when incoming errors arrive after maybe_cleanup() runs. Fixed a bug where notify would lose original error values by ensuring it no longer attempts to decode empty responses. Enhanced io_context shutdown procedures to clear handlers and route cleanl ## A 10 GB Memory Leak Killed My Bluetooth Trackpad: bluetoothd -experimental on Ubuntu DevFeed: [A 10 GB Memory Leak Killed My Bluetooth Trackpad: bluetoothd -experimental on Ubuntu]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-05-27T10:09:00Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Bluetooth](), [Memory Leaks](), [Ubuntu](), [Linux](), [Processes]() Tags: [apple-magic-trackpad](), [bluetooth](), [experimental](), [memory-leak](), [process](), [ubuntu]() ### AI overview The article investigates a bluetoothd memory leak on Ubuntu 25.10 associated with the -experimental flag. It describes a Bluetooth trackpad failure after three days of uptime, reports bluetoothd using 10.3 GB of RAM, and presents diagnostic commands and a one-line fix. ### Source excerpt How a runaway bluetoothd process -- silently leaking memory for three days under the -experimental flag -- quietly killed my Apple Magic Trackpad on Ubuntu 25.10, what the symptoms looked like, and the one-line fix that brought everything back. ## Haiku Activity & Contract Report, April 2026 DevFeed: [Haiku Activity & Contract Report, April 2026]() Original publisher: [Read original article]() Author: waddlesplash Published: 2026-05-12T03:30:00Z Content type: article Language: en Sources: [Haiku Project]() Topics: [Code](), [JSON Schema](), [Command-line interface](), [Memory Leaks](), [bug]() Tags: [2026](), [activity-report](), [bug](), [code](), [command-line](), [contractor](), [json-schema](), [memory-leak](), [report]() ### AI overview Haiku's April 2026 activity and contract report covers revisions hrev59570 through hrev59671, documenting performance improvements, bug fixes, memory-leak fixes, JSON Schema code-generation work, and command-line tool changes. ### Source excerpt This report covers hrev59570 through hrev59671. GSoC selection happened at the end of last month; you can read the news post announcing this year's selectees. Thanks to everyone who applied! Applications phoudoin disabled some redundant filetype checking in TextSearch, improving performance a bit. nipos dropped some obsolete code from WebPositive's tab bar. jscipione continued his work on Tracker, removing redundant code, fixing problems with Copy/Paste, the Trash icon, and much more. waddlesplash came by and made a few fixes too, including one to avoid a lot of unnecessary node monitoring syscalls. aquamatic123 did some cleanups to the Devices internals, solving another TODO. He also tracked down and fixed a memory leak. apl refactored the JSON schema code generation system in HaikuDepot, to prepare for potential use with REST APIs (among other reasons.) He also fixed the "Featured" tab displaying as disabled incorrectly in some circumstances (which also entailed fixing a bug in BTabView), and reworked how the package view data is updated. humdinger removed some unnecessary spacing in the Appearance preferences. jscipione made the message body text colors in Mail automatically update when the system colors change. nathan242 fixed a crash in SoftwareUpdater when trying to quit while a download was running. waddlesplash implemented automatic cleanup of the "admin" directory in it, meaning that older states will now automatically be deleted to free up space (unless the setting is disabled.) jscipione cleaned up some code and added some missing functions to DeskCalc's math backend. Command line tools waddlesplash improved the (not yet ready for general use) ltrace implementation, fixing a number of TODOs and inefficiencies. However, it's still not ready for general consumption, as it causes problems and crashes when it traces calls. waddlesplash split the "clean up admin directory" functionality of pkgman into a separate subcommand (pkgman cleanup), and changed install ## Hunting iOS Memory Leaks: S1E1 DevFeed: [Hunting iOS Memory Leaks: S1E1]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2026-05-09T09:43:49Z Content type: article Language: en Sources: [Amanjeet Singh]() Topics: [Memory Leaks](), [iOS](), [Automation](), [GitHub Actions](), [Claude Code](), [test]() Tags: [automation](), [claude-code](), [engineering](), [github-actions](), [ios](), [memory](), [memory-leak](), [memory-leaks](), [mobile](), [traces](), [unit-test]() ### AI overview The first edition of Hunting Memory Leaks describes development of XCTestLeaks, a tool that runs unit test schemes, checks for retain cycles with leaks(1), and produces HTML leak reports. The author reports fixing two memory leaks in Firefox-iOS-related code and outlines a workflow using project-specific GitHub Actions, Claude Code, and optional upstream issues or pull requests. ### Source excerpt Welcome to the first edition of Hunting Memory Leaks. Another wild week, mostly battling with XCTestLeaks, the tool I've been building on the side. I'll release it once I'm confident the workflow holds up across at least 5 repos. For context, I've ## Heaps do lie: debugging a memory leak in vLLM. DevFeed: [Heaps do lie: debugging a memory leak in vLLM.]() Original publisher: [Read original article]() Published: 2026-01-21T16:00:00Z Content type: article Language: en Sources: [Mistral AI Blog]() Topics: [Memory Leaks](), [vllm](), [debug](), [Inference](), [Grafana]() Tags: [cache](), [debugging](), [deep-dive](), [engineering](), [grafana](), [inference](), [memory](), [vllm]() ### AI overview Mistral AI investigates a vLLM memory leak that appeared during pre-production testing of disaggregated serving with Mistral Medium 3.1 and graph compilation enabled. The investigation moved from Python-level tools to kernel-level tracing and identified KV Cache transfer through NIXL in the decode side of a Prefill/Decode setup as the likely root cause. ### Source excerpt The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models. ## Quality Week - December 2025 DevFeed: [Quality Week - December 2025]() Original publisher: [Read original article]() Author: Katie Geer, Joseph Lyons Published: 2026-01-09T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Optimization](), [GPU](), [Git](), [macOS](), [pull-requests](), [Markdown](), [Terminal](), [Memory Leaks](), [Tree-sitter](), [ssh]() Tags: [git](), [improvements](), [macos](), [markdown](), [memory-leak](), [performance](), [pull-requests](), [speed](), [ssh](), [terminal]() ### AI overview Zed's December 2025 Quality Week focused on bug fixes, performance improvements, and small quality-of-life features. The team closed 64 issues and merged 169 pull requests, including changes to Markdown editing, GPU rendering on macOS, terminal scrolling, large-file performance, agent-panel model selection, and memory leaks. ### Source excerpt A look at what the Zed team and community accomplished during our December 2025 Quality Week, focusing on stability, performance, and polish. ## Discovering iOS Memory Leaks IV: Detecting via Unit Tests DevFeed: [Discovering iOS Memory Leaks IV: Detecting via Unit Tests]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2026-01-07T01:46:06Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [iOS](), [Memory Leaks](), [unit tests](), [Xcode](), [macOS]() Tags: [ios](), [macos](), [memory](), [memory-leak](), [memory-leaks](), [tests](), [unit-tests](), [xcode]() ### AI overview This article explores detecting real iOS memory leaks with unit tests instead of UI tests. It describes running the macOS leaks tool against the Firefox process during unit-test teardown in the iOS simulator to shorten the feedback cycle and broaden coverage. ### Source excerpt Using unit tests and macOS leaks tool to catch real iOS memory leaks. ## Wednesday, May 14, 2025 Security Releases DevFeed: [Wednesday, May 14, 2025 Security Releases]() Original publisher: [Read original article]() Published: 2025-05-14T03:00:00Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [releases](), [Security](), [vulnerability](), [Memory Leaks](), [DDoS](), [Parser](), [Windows]() Tags: [2025](), [http](), [memory](), [node](), [node-js](), [open-source](), [release](), [releases](), [security](), [vulnerability](), [windows]() ### AI overview The Node.js Project announced security releases for the 24.x, 23.x, 22.x, and 20.x release lines on May 14, 2025. The updates address vulnerabilities involving cryptographic operations in background threads, HTTP request smuggling in Node.js 20, and an unrecoverable memory leak affecting specific Windows configurations. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Subverting control with weak references DevFeed: [Subverting control with weak references]() Original publisher: [Read original article]() Author: James Long Published: 2025-02-24T12:00:00Z Content type: tutorial Language: en Sources: [James Long]() Topics: [JavaScript](), [Data structures](), [Memory Leaks]() Tags: [article](), [data-structure](), [javascript](), [memory](), [memory-leaks](), [reference]() ### AI overview This JavaScript article explains weak references, WeakRef, and WeakMap. It describes how weak references interact with garbage collection and how WeakMap can avoid retaining objects and causing memory leaks. ### Source excerpt Weak references are neat. The best language features unlock different kinds of abstractions, and weak references do exactly that. Let me show you why. In JavaScript we have two APIs to work with weak references: WeakMap and WeakRef. (Before I wrote this article I thought WeakRef was only a proposal, but it turns out most browsers have already implemented it) One of the more common use cases uses WeakMap. This data structure keeps a weak reference to the keys in the map, and a strong reference between the keys and values. I guess I should explain what a "weak reference" is: usually if you have a reference to an object in a variable, it stops the garbage collector from deleting it (which makes sense). It'd be weird if suddenly your variable pointed to nothing right? A "weak reference" doesn't stop the object from being garbage collected. Usually languages' semantics don't allow a variable to change in the middle of execution however: // this doesn't exist, but what if we could create a weak reference like this? let weak trans = new Transaction(); // do a bunch of things... // error! trans is... nothing? it got garbage collected trans.transfer(); ^3d7637 Wouldn't it be weird if trans changed in the middle of execution? If that was possible all bets would be off for everything in the entire program because these weak references could be passed anywhere. Instead, APIs for weak references force you to call a function to get the value. The WeakRef class has a deref method to get the object. const ref = new WeakRef(obj) // get the object ref.deref() // do a bunch of things... ref.deref() ^ae238d In the above example, if nothing has a reference to obj, it'll eventually get garbage collected. That means deref might return obj the first time, but the second time it might return undefined. Let's get back to WeakMap which is the more common usage of weak references. (Direct weak references have a lot of weird behaviors and they should be considered very low-level.) A WeakMap has ## Simplify ViewBinding in Android with ViewBindingPropertyDelegate 2.0 DevFeed: [Simplify ViewBinding in Android with ViewBindingPropertyDelegate 2.0]() Original publisher: [Read original article]() Author: Kirill Rozov Published: 2025-02-04T13:30:45Z Content type: release Language: en Sources: [Stories by Kirill Rozov on Medium]() Topics: [Android](), [Library](), [Jetpack](), [Refactoring](), [Memory Leaks](), [recyclerview]() Tags: [android](), [android-jetpack](), [fragments](), [jetpack](), [library](), [memory-leaks](), [open-source](), [performance](), [recyclerview](), [refactoring](), [release](), [ui](), [view-binding]() ### AI overview This article announces ViewBindingPropertyDelegate 2.0, a release that refactors how the Android library manages ViewBinding lifecycles. It replaces Jetpack Lifecycle-based detection with component lifecycle callbacks for Fragments and Activities, improving the timing of reference clearing and addressing issues related to Fragment animations. The release also supports lazy ViewBinding creation and aims to prevent memory leaks. ### Source excerpt I'm excited to announce the release of ViewBindingPropertyDelegate 2.0, which introduces significant under-the-hood refactoring to enhance the library's stability and performance. In this article, I'll highlight the most important changes and explain how they improve the library's functionality. Brief Introduction ViewBindingPropertyDelegate(VBPD) is a lightweight library designed to simplify the use of Android's ViewBinding by: Managing the ViewBinding lifecycle and clearing references to prevent memory leaks. Eliminating the need to maintain nullable references to Views or ViewBindings. Creating ViewBindings lazily. The library supports usage in various components, including Activities, Fragments, ViewGroups, and RecyclerView.ViewHolders. class ProfileFragment : Fragment(R.layout.profile) { private val profileBinding: ProfileBinding by viewBinding(ProfileBinding::bind) override fun onViewCreated(view: View, savedInstanceState: Bundle?) { super.onViewCreated(view, savedInstanceState) // ProfileBinding instance will be created lazily on first access profileBinding.name.text = ... } override fun onDestroyView() { super.onDestroyView() // profileBinding reference will be cleared after onDestroyView() } }Changes in 2.0Transition from Lifecycle to Component Callbacks In previous versions (1.x), VBPD relied on Jetpack's Lifecycle to detect when a View was being destroyed. This approach had a limitation: the Lifecycle callback methods could be invoked before Fragment.onDestroyView(), while the ViewBinding reference was still needed. To address this, VBPD postponed clearing the ViewBinding reference using an Android Handler after onDestroyView(), when the Fragment's View LifecycleOwner transitioned to the DESTROYED state. In version 2.0, VBPD now utilizes FragmentManager.FragmentLifecycleCallbacks to detect when a Fragment's view is destroyed. The key difference lies in the timing of these callbacks, allowing for more precise management of the ViewBinding lifecycle. // Sou ## Discovering iOS memory leaks III: Automating with Github Action DevFeed: [Discovering iOS memory leaks III: Automating with Github Action]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2024-12-01T10:28:06Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [Memory Leaks](), [GitHub Actions](), [iOS](), [Command-line interface](), [GitHub](), [test](), [Processes](), [Xcode]() Tags: [cli](), [github](), [github-actions](), [ios](), [macos](), [maestro](), [memory-leak](), [pipeline](), [process](), [test](), [tests](), [xcode](), [yaml]() ### AI overview This third article in a series explains how to automate iOS memory-leak detection in a CI pipeline using GitHub Actions. It covers setting up a macOS runner, building and installing Firefox iOS, launching the app and running a Maestro test, invoking the leaks command, uploading reports, and using a baseline to distinguish known leaks from newly introduced ones. ### Source excerpt Automating Leak Detection with Github Action ## Docusaurus 3.6 DevFeed: [Docusaurus 3.6]() Original publisher: [Read original article]() Author: Sébastien Lorber Published: 2024-11-04T00:00:00Z Content type: release Language: en Sources: [Docusaurus Blog]() Topics: [build performance](), [build times](), [Memory Leaks](), [Compiler](), [Rust]() Tags: [build-performance](), [build-times](), [bun](), [ci](), [memory-leak](), [npm](), [pnpm](), [release]() ### AI overview Docusaurus 3.6 introduces the opt-in Docusaurus Faster infrastructure project, using Rust-based tools to improve build performance and reduce memory consumption. Community benchmarks report production builds that are 2 to 4 times faster, alongside a fixed memory leak and smaller static HTML output. ### Source excerpt We are happy to announce Docusaurus 3.6. ## Identifying insecure C Code with Valgrind and fixing with Snyk Code DevFeed: [Identifying insecure C Code with Valgrind and fixing with Snyk Code]() Original publisher: [Read original article]() Author: Liran Tal Published: 2024-09-24T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [C](), [Static code analysis](), [Memory Leaks](), [Vulnerabilities](), [C++](), [Security](), [snyk-code]() Tags: [analysis](), [awareness](), [blog](), [c](), [c-cpp](), [c-plus-plus](), [code-security](), [developer](), [devops](), [devrel](), [docker](), [how-to](), [memory-leaks](), [memory-management](), [programming](), [security](), [snyk-code](), [vulnerabilities]() ### AI overview This tutorial explains how insecure C and C++ code can introduce memory leaks and other vulnerabilities, and describes using Valgrind and Snyk Code's static code analysis to identify and fix them. It also discusses dynamic memory allocation, memory exhaustion, and relevant MISRA guidance. ### Source excerpt Discover how to secure your C and C++ code with Snyk. Learn about common vulnerabilities like memory leaks and buffer overflows in C and C++ and how Snyk's static code analysis tool can help you identify and fix them. Protect your critical software from security threats. [Next page]()