This guide explains what a Core Dump is, why it is essential for Linux crash analysis, how the kernel creates it, common signals that trigger it, typical causes of crashes, and step‑by‑step configuration and GDB techniques to capture and debug Core Dump files effectively.
This guide explains what kdump is, how it works, and provides step‑by‑step instructions for installing, configuring, and verifying kdump on Linux systems, plus tips for analyzing vmcore files with crash and GDB.
This article walks through a real‑world Android crash case, showing how to collect crash data with RUM, trace the user journey, analyze stack traces, identify the root cause in ProductListAdapter, and apply symbolication to turn obfuscated stacks into readable code.
This article walks through a real‑world Android crash investigation, showing how to collect, visualize, and analyze crash data with Alibaba Cloud RUM, trace user behavior, identify the root cause in ProductListAdapter, and apply symbolication and version comparison to resolve the issue efficiently.
The 2025 Bugly HarmonyOS Quality Report analyzes system version adoption, device distribution, crash and freeze rates across industries, identifies top stability issues such as memory leaks and main‑thread blocking, and offers concrete optimization recommendations for developers seeking better app performance.
This article analyzes a recurring crash in Android mini‑programs caused by a canvas synchronization issue in hybrid composition, detailing the stack traces, EGL surface creation failures, cross‑process SurfaceTexture lifecycle problems, and the concrete fix that dramatically reduced “no surface” crashes.
This article analyzes a driver‑side iOS 18 crash triggered by BackBoardServices calling exit, explains the underlying XPC and C++ destructor chain, explores failed hook and compiler‑flag workarounds, and presents a reliable atexit‑based solution that eliminates the crash on iOS 18 and later.
This article explains how Windows minidump files are organized, detailing the header, key stream types such as ThreadListStream, ModuleListStream, ExceptionStream, SystemInfoStream, and MiscInfoStream, and shows how to extract useful crash information for debugging.
This article walks through the anatomy of a Java Virtual Machine crash, explains how to read the generated hs_err_pid log and core dump, and provides practical debugging steps—including code examples, signal analysis, register context, and GDB commands—to pinpoint and resolve the root cause.
The Didi Android delivery merchant app suffered periodic crashes on Huawei devices because a null‑checked fopen in libpush.so caused an unchecked fwrite, leaking file handles until the per‑process limit was reached, and the issue was resolved by adding proper null checks, closing handles, and instituting systematic FD‑leak monitoring and code‑review safeguards.
The crash in asl::LooperObserverMan::notifyIdle was traced to a compiler‑level store‑store reordering that exposed an uninitialized observer pointer, causing an illegal memory access, and was fixed by inserting a memory barrier or using proper atomic ordering to enforce correct initialization order.
The article explains the design of Meituan’s MySQL autonomous platform, detailing its four‑layer architecture, statistical dynamic‑threshold anomaly detection, model selection based on time‑series distribution, kernel‑level root‑cause analysis for replication lag, large‑transaction diagnostics, and crash investigation using core‑dump and signal analysis.
An original case study examines a MongoDB 4.0.14 replica set crash triggered by exceeding the WiredTiger session limit when a primary creates a background index and subsequently drops it, causing blocking on the secondary, leading to connection saturation, session exhaustion, and instance failure.
The article investigates a rapid increase in WebView crashes on iOS 4.9.x caused by a UIScrollView animation accessing a released object after an H5 page is dismissed, discovers the offending WKChildScrollView delegate (WKScrollingNodeScrollViewDelegate), and resolves the issue by nullifying that delegate in the view’s deallocation, supplementing earlier gesture‑disable workarounds.
This article explains how GWP‑ASan, a low‑overhead sampling memory‑sanitizer developed by Google, can be integrated on Windows to detect heap errors such as use‑after‑free, buffer‑underflow, buffer‑overflow and double‑free, describes its monitoring principles, hook implementation, crash‑report augmentation, and presents real‑world case studies and remediation strategies.
This article details Quark iOS's systematic stability effort in 2022, describing how the team identified top JavaScriptCore crashes, traced them to memory‑leak and AppWorker issues, applied targeted feature toggles, upgraded SDKs, and ultimately achieved a sharp drop in overall crash rates.
This article explains what SIGKILL crashes are on iOS, how the operating system terminates a process, how to capture SIGKILL events using the MetricKit framework with code examples, the meaning of common termination codes, and practical fixes for typical SIGKILL scenarios in mobile apps.
A SIGKILL crash indicates the OS forcibly terminated an iOS app, which cannot be caught directly, but MetricKit (iOS 14+) can automatically collect diagnostic payloads after restart, allowing developers to extract termination reasons, stack traces, understand codes like 0x8badf00d, and address common causes such as main‑thread watchdog timeouts and deadlocks.
This article presents a comprehensive framework for identifying, classifying, and resolving iOS stability issues—covering crash types, governance methodology, deep-dive attribution techniques, real-world case studies, and practical tools such as Zombie monitoring, Coredump, MemoryGraph, and MetricKit—to dramatically improve app reliability.
This article presents a comprehensive guide on systematically managing iOS stability problems, covering issue classification, a governance methodology, detailed root‑cause analysis for crashes, watchdogs, OOM, CPU and disk I/O anomalies, and practical tools and case studies from ByteDance’s APM platform.
This article explains what symbolication is, how to generate and match dSYM files, perform local symbolication with Xcode or the symbolicatecrash tool, extract system library symbols from devices or firmware, and implement fast online symbolication for massive iOS crash logs.
This guide explains why raw iOS crash logs are unreadable, introduces dSYM files and DWARF debugging information, shows how to match UUIDs, compute addresses, and use both Xcode and command‑line tools for local symbolication, and describes a scalable online solution for massive crash‑log processing.
The article discusses identifying and resolving ImageIO-related crash issues in iOS applications, particularly those occurring after iOS 14 updates, by analyzing crash logs and system behavior.
The article explains how Android’s debuggerd daemon registers signal handlers, captures crashes, generates detailed tombstone files containing process, thread, register and memory information, and provides a step‑by‑step method for analyzing these files with tools like addr2line and objdump to locate the fault.
This article explains the background, advantages, implementation details, and crash analysis of using SwiftMonkey and XCUITest for lightweight, automated iOS Monkey testing, providing code examples and outlining pending improvements for a more robust testing pipeline.
This article explains how to investigate a MySQL crash when core dumps are disabled by extracting the crash address from the error log, obtaining the matching binary, using GDB to map the address to source code, and decoding encoded function signatures to pinpoint the underlying bug.
Android captures uncaught Java exceptions using Thread.UncaughtExceptionHandler, first logging details with a system LoggingHandler then terminating the app via KillApplicationHandler, converting the Throwable into an ApplicationErrorReport sent to ActivityManagerService and stored in /data/system/dropbox, while developers can view the same FATAL EXCEPTION stack trace in logcat to diagnose and fix the root cause.
This article explains why operating system and driver defects cause system hangs and reboots, introduces the methodology of memory dump analysis—including deadlock and exception techniques—and walks through a real Linux kernel panic case to illustrate how to trace, diagnose, and remediate such crashes.
This guide demonstrates how to reproduce a MySQL crash, enable system‑level core dumps, adjust user limits, configure MySQL to generate core files, and use gdb to extract useful debugging information for complex failure analysis.
This article introduces the background, core features, network and page performance modules, error monitoring, reporting, and optimization practices of a mobile App Performance Management (APM) system, highlighting its impact on monitoring, diagnostics, and performance improvement for large‑scale applications.
The article investigates a sporadic iOS app startup timeout where the process is killed by the system, analyzes crash logs showing a SIGKILL (0x8badf00d) watchdog termination, traces the issue to excessive UIPasteboard calls made by OpenUDID in both main and background threads, validates the hypothesis with multi‑threaded tests, surveys SDK usage of OpenUDID, and proposes moving the identifier storage to the keychain to avoid clipboard‑induced hangs.
After a 2018 Flutter upgrade caused a mysterious “Ghost Crash” in Xianyu’s app, engineers traced an over‑released NSMutableArray in the accessibility bridge, fixed an illegal dealloc call, added proper checks for iOS Speak Screen, and eliminated the crash through a rapid gray‑scale rollout.
This article explains how to capture Android device logs using adb commands, export them, combine with monkey testing, and then analyze logcat output—including ring buffers, priority levels, and common crash or ANR patterns—to efficiently locate and resolve issues.
JD Security presents a series of AI‑driven security innovations—including black‑box explanation methods, deep‑learning crash analysis, AI‑vs‑AI e‑commerce fraud defenses, and open‑source collaboration—to illustrate how artificial intelligence can be made transparent, effective, and safely integrated into modern security operations.
This article investigates an Android JNI native crash caused by misusing NewString(), examines why a custom UTF‑8‑to‑UTF‑16 conversion was used instead of NewStringUTF(), compares Dalvik and ART string encodings, reveals a Dalvik UTF‑8 conversion bug fixed in ART, and advises developers on encoding nuances across Android versions.
This article examines why an inline hook created with Substrate on ARM Thumb crashes, detailing the hook mechanism, the offending PC‑relative ADR instruction, and the necessary instruction fixes to prevent control‑flow errors.
The 2016 Android & iOS Mobile App Quality Report shows a surge in device numbers, highlights higher crash rates for games versus apps, identifies common exceptions like NullPointerException, outlines manufacturer market shares, OS version distribution, and offers actionable insights for developers to improve stability across platforms.
This article explains how to design a complete mobile app monitoring framework that covers problem discovery through key quality metrics and user feedback, systematic log instrumentation, effective issue localization methods, and rapid damage‑control strategies such as cloud‑based feature toggles and hot‑fix mechanisms.
