# Memory Leak Published articles for Memory Leak. 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... ## 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. ## 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. ## 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 ## 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 ## 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. ## Blog: Introducing Falco 0.42.0 DevFeed: [Blog: Introducing Falco 0.42.0]() Original publisher: [Read original article]() Published: 2025-10-22T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [container](), [Processes](), [static linking]() Tags: [bug](), [bug-fixes](), [dry-run](), [falco](), [features](), [memory-leak](), [performance](), [recording](), [release](), [static-linking]() ### AI overview Falco 0.42.0 introduces a capture recording feature that generates .scap files when detection rules trigger, including system-call traces for forensic analysis. The release also includes performance improvements, schema validation, configuration changes, and bug fixes. ### Source excerpt Dear Falco Community, today we are happy to announce the release of Falco 0.42.0! This release brings exciting new capabilities, including the capture feature, significant performance improvements, and important bug fixes that enhance Falco's capabilities. During this release cycle, we merged: 52 PRs on Falco, including 23 release note-worthy changes 110 PRs on Falco libs, including 47 release note-worthy changes 102 PRs on Falco drivers, including 29 release note-worthy changes We upgraded libs to version 0.22.1 and drivers to v9.0.0+driver. Thank you to our maintainers and contributors. This would not have been possible without your support and dedication! To learn everything about the changes, read on! What's new? TL;DR Key features: Capture recording feature; Drop enter initiative for performance; Plugin event schema validation; Thread table auto-purging configuration; Static fields; Key fixes: Fix thread table memory leak when parsing vfork (or equivalent clone/clone3 with CLONE_VFORK) exit from the caller process; Enable handling of multiple actions configured with syscall_event_drops.actions; Disable dry-run restarts when Falco runs with config-watching disabled; Fix abseil-cpp for Alpine build; Fix detection sandbox containers for CRI and containerd runtimes (container plugin); Stability improvements for container plugin and static linking of libgcc/libstdc++ for legacy compatibility; This release also comes with breaking changes that you should be aware of before upgrading. Major features and improvements The 0.42.0 release contains a new capture feature and significant performance improvements. Here is a list of the key new capabilities. Capture recording feature Falco 0.42.0 introduces the new capture recording feature, now available at sandbox maturity. This capability allows Falco to generate .scap files whenever a detection rule is triggered automatically. Each capture contains a detailed trace of system calls around the event, providing forensic-level ## 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. ## Testing LeakCanary 3 heap-growth detection with the Slack Android app DevFeed: [Testing LeakCanary 3 heap-growth detection with the Slack Android app]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2024-05-07T00:47:25Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Android](), [App](), [Testing](), [Emulator](), [Gradle]() Tags: [android](), [android-studio](), [app](), [article](), [droidcon](), [emulator](), [gradle](), [leakcanary](), [memory-leak](), [performance](), [slack](), [testing]() ### AI overview The article describes a preview LeakCanary 3 toolkit that detects heap growth by comparing repeated heap dumps and tracking objects with increasingly many outgoing edges. It explains how to run the tool against the Slack Android app using an emulator and UI Automator, but the supplied text ends before the results are presented. ### Source excerpt In this article I run the new LeakCanary toolkit against the Slack Android app. Read on to learn a bunch! A new LeakCanary toolkit In two months, I will give a talk at Droidcon SF: Cutting Edges: universal heap trimming with LeakCanary 3 At Square, ... ## Stressing the JVM GC on Android DevFeed: [Stressing the JVM GC on Android]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2024-03-10T08:49:55Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [Android](), [Java](), [Code](), [now-in-android]() Tags: [adb](), [android](), [android-vitals](), [anr](), [fragmentation](), [gc](), [java](), [leak](), [memory](), [memory-leak](), [mobile](), [mobile-performance](), [now-in-android](), [outofmemory](), [performance](), [stress](), [stresstest]() ### AI overview This tutorial describes GCStress, a Java application that deliberately creates garbage-collection pressure through repeated random byte-array allocations and cache removals. It explains how to integrate it into Google's Now in Android app, trigger it with an Android broadcast and adb, and observe effects such as skipped UI frames, possible ANRs, and potential out-of-memory errors. ### Source excerpt This post talks about a way to stress Java garbage collector. ## Investigating a Ruby Memory Leak in the HEY App DevFeed: [Investigating a Ruby Memory Leak in the HEY App]() Original publisher: [Read original article]() Author: Jacopo Beschi Published: 2024-03-07T18:00:00Z Content type: tutorial Language: en Sources: [37signals Dev]() Topics: [Memory Leaks](), [Ruby](), [App](), [Server]() Tags: [app](), [gc](), [load-balancer](), [memory-leak](), [ruby](), [trace]() ### AI overview This article describes how a team investigated a slow Ruby memory leak in the HEY app. It covers analyzing Ruby heap allocation statistics, extracting heap dumps with rbtrace, enabling object allocation tracing, and comparing dumps over time while limiting the diagnostic impact to one app host. ### Source excerpt What I learned on the journey chasing a tricky memory leak in HEY. ## Discovering iOS memory leaks: A case study with Firefox app II DevFeed: [Discovering iOS memory leaks: A case study with Firefox app II]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2024-02-24T11:22:22Z Content type: article Language: en Sources: [Amanjeet Singh]() Topics: [Firefox](), [iOS](), [Memory Leaks](), [Open Source](), [Pull Request](), [GitHub](), [Refactoring]() Tags: [firefox](), [github](), [ios](), [leak](), [memory](), [memory-leak](), [memory-leaks](), [mobile-performance](), [open-source](), [release]() ### AI overview A case study of contributing a memory-leak fix to Firefox for iOS. The article describes the pull-request process, an initially unmerged approach, the eventual fix involving a UI kit retain cycle, and lessons about coordinating with open-source maintainers. ### Source excerpt Discover my experience in contributing to Firefox ios fixing their memory leaks ## Choosing Good SLIs DevFeed: [Choosing Good SLIs]() Original publisher: [Read original article]() Published: 2024-02-19T21:11:17Z Content type: opinion Language: en Sources: [Brave New Geek]() Topics: [Cloud](), [monitor](), [on-prem](), [autoscaling](), [systems]() Tags: [autoscaling](), [cloud](), [devops](), [garbage-collection](), [kubernetes](), [latency](), [memory-leak](), [monitor](), [monitoring](), [on-prem](), [ops](), [service-level-agreements](), [software-engineering](), [sre]() ### AI overview The article explains why organizations moving from on-premises environments to the cloud should reevaluate their Service Level Indicators (SLIs). It argues that resource-focused metrics and operational patterns from data centers may be less useful in cloud environments, where autoscaling, autohealing, ephemeral instances, and different infrastructure characteristics can obscure application issues. ### Source excerpt Transitioning from an on-prem environment to a cloud environment involves a lot of major shifts for organizations. One of those shifts is often around how we monitor the overall health of systems. The typical way to measure things like the availability, reliability, and performance of systems is with SLIs or Service Level Indicators. SLIs are a valuable tool both on-prem and in the cloud, but when it comes to the latter, I often see organizations carrying over some operational anti-patterns from their data center environment. ## OutOfMemoryError on Android: heap dump recording DevFeed: [OutOfMemoryError on Android: heap dump recording]() Original publisher: [Read original article]() Author: Vadzimv Dev Blog Published: 2024-01-07T11:00:00Z Content type: tutorial Language: en Sources: [vadzimv Dev Blog]() Topics: [Android](), [debugging](), [Java](), [Memory Leaks](), [Android Studio](), [Crashlytics]() Tags: [android](), [android-studio](), [debugging-tools](), [firebase](), [how-to](), [java](), [memory-leak]() ### AI overview This tutorial explains how to automatically record a Java heap dump when an OutOfMemoryError occurs in an Android application. It covers heap-dump collection, uncaught-exception handling, Android storage, and subsequent analysis. ### Source excerpt Learn how to record a Java heap dump at the moment of OutOfMemoryError. ## Discovering iOS memory leaks: A case study with Firefox app DevFeed: [Discovering iOS memory leaks: A case study with Firefox app]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2023-12-25T21:07:16Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [iOS](), [Memory Leaks](), [Command-line interface](), [Firefox](), [App](), [Monitoring]() Tags: [command-line](), [crashlytics](), [firebase](), [firefox](), [ios](), [leak](), [memory](), [memory-leak](), [memory-leaks](), [tool]() ### AI overview A case study on detecting and prioritizing memory leaks in iOS apps. It explains automatic reference counting, recommends prioritizing production leaks and monitoring core flows, and uses a Firefox iOS app with UI tests and the macOS leaks command-line tool. ### Source excerpt Discover how to efficiently detect and manage memory leaks in iOS apps using the leaks command line tool with example ## Apollo Client 3.9 Feature Spotlight - The memory story DevFeed: [Apollo Client 3.9 Feature Spotlight - The memory story]() Original publisher: [Read original article]() Author: Lenz Weber-Tronic Published: 2023-12-20T16:02:32Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [Memory Leaks](), [Caching](), [Open Source](), [Maintainers]() Tags: [apollo-client](), [cache](), [feature](), [issue](), [leak](), [memory](), [memory-leak](), [memory-leaks](), [open-source](), [spotlight]() ### AI overview Apollo Client 3.9 is released in beta with fixes for various memory leaks, more granular control over internal cache sizes, and deprecation of canonizeResults because of a conceptual, non-fixable memory leak. The article also asks users to help determine appropriate default cache sizes. ### Source excerpt Apollo Client 3.9 is out in beta now, and it fixes various memory leaks, adds granular control over internal cache sizes, and deprecates the canonizeResults option due to a conceptual and non-fixable memory leak associated with it. We want your help to find the correct default cache sizes - see the last paragraph for details on that. The memory story Sometimes, in an open source project, you have that issue that sticks around for a long time because it's not clear how you would tackle it. ## How Android Memory Leaks Cause Jank, Freezes, and ANRs DevFeed: [How Android Memory Leaks Cause Jank, Freezes, and ANRs]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2023-07-20T22:09:53Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Android](), [Memory Leaks](), [Latency](), [navigation](), [Java]() Tags: [android](), [jank](), [latency](), [main-thread](), [memory-leak](), [memory-leaks](), [navigation](), [outofmemory](), [performance]() ### AI overview This article explains how Android memory leaks can cause jank, freezes, and ANRs rather than immediate crashes. It describes tracking memory usage per navigation, correlating memory growth with navigation latency, and how garbage collection blocking the main thread affects UI responsiveness near the app memory limit. ### Source excerpt In this article, I show how Android memory leaks lead to jank, freezes and ANRs more often than they lead to OutOfMemoryError crashes. Navigation Latency At Square, we've been tracking a User-Centric performance metric: Interaction Latency. We track ... ## Avoid Java double brace initialization DevFeed: [Avoid Java double brace initialization]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2023-06-27T20:58:00Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Java](), [Code](), [Android]() Tags: [android](), [class](), [classes](), [code](), [constructor](), [crash-reporting](), [gc](), [global](), [implementation](), [java](), [leak](), [leakcanary](), [lifecycle](), [memory](), [memory-leak](), [object](), [patterns](), [subclass]() ### AI overview This tutorial explains how Java double brace initialization can cause memory leaks. An anonymous HashMap subclass implicitly retains its outer Activity, so a breadcrumb stored by a singleton BugSnag client can keep a destroyed Android Activity in memory. The article recommends avoiding the pattern and using explicit initialization or Kotlin. ### Source excerpt TL;DR Avoid doing this: new HashMap() {{ put("key", value); }}; Leak Trace I was recently looking at the following leak trace from LeakCanary: ┬─── │ GC Root: Global variable in native code │ ├─ com.bugsnag.android.AnrPlugin instan... ## God writes Haskell DevFeed: [God writes Haskell]() Original publisher: [Read original article]() Published: 2023-06-02T22:00:00Z Content type: opinion Language: en Sources: [Dennis Felsing]() Topics: [Haskell](), [quantum mechanics](), [Programming](), [Compiler](), [Data structures]() Tags: [arrays](), [compiler](), [haskell](), [memory-leak](), [programming](), [quantum](), [quantum-mechanics](), [type-system]() ### AI overview A humorous commentary compares Haskell concepts--including lazy evaluation, immutability, linked lists, type checking, and memory retention--to ideas from quantum mechanics and the physical universe. ### Source excerpt God famously does not play dice with the universe, but he seems to enjoy writing Haskell: Consider the wave-particle duality in quantum mechanics. Every particle behaves as a wave, as long as you haven't interacted with it. Thanks to Haskell's lazy evaluation values are also only evaluated once they are accessed (interacted with particles), and stay unevaluated thunks (waves) in the meantime. Two particles can be Quantum-entangled, so that their states depend on each other, even though the particles are seperated by any distance. In Haskell a value, whether it's evaluated yet or not, can also be shared and then used in a totally different location in the program without having to copy it. The value is even immutable, so that you can't change it from one location and thus influence the other. Similarly for entangled particles you can't manipulate one to change the state of the other particle, which might be far away and thus break the maximum speed of information. Since values are immutable they have to be cleaned up more often in Haskell than typically in imperative languages. GHC, the most commonly used Haskell compiler, allocates new data in a special area. Only after a supernova will the still-relevant data be ejected into the larger universe. Haskell beginners often use lists instead of arrays. You can't do random access in a linked list, but only access the first element and then the rest of the list. The real world also doesn't allow you random access, you are limited by the speed of light and have to go from one location to the next. Time also seems to be a linked list, not even doubly linked, since you can't go back after accessing the current element. Seems like an awkward bug. Since the Haskell type system is so good at catching bugs, you often feel like you don't even need to write tests. This is unfortunately untrue, as the strange physical bugs of our universe demonstrate: The speed of light happens to stay the same, no matter what speed you move at. Th ## Finding Java Thread Leaks With JDK Flight Recorder and a Bit Of SQL DevFeed: [Finding Java Thread Leaks With JDK Flight Recorder and a Bit Of SQL]() Original publisher: [Read original article]() Published: 2023-02-28T21:16:10Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [JDK Flight Recorder](), [Java](), [Concurrency](), [Memory Leaks](), [SQL]() Tags: [java](), [jdk](), [jdk-flight-recorder](), [memory-leak](), [performance-analysis](), [root-cause-analysis](), [sql](), [thread](), [threads]() ### AI overview This article explains how to investigate Java thread leaks with JDK Flight Recorder. It describes why thread leaks can cause memory and CPU problems, why thread dumps are limited, and how JFR events can reveal changing thread counts and the source of newly created threads. ### Source excerpt The other day at work, we had a situation where we suspected a thread leak in one particular service, i.e. code which continuously starts new threads, without taking care of ever stopping them again. Each thread requires a bit of memory for its stack space, so starting an unbounded number of threads can be considered as a form of memory leak, causing your application to run out of memory eventually. In addition, the more threads there are, the more overhead the operating system incurs for scheduling them, until the scheduler itself will consume most of the available CPU resources. Thus it's vital to detect and fix this kind of problem early on. [Next page]()