Tagged articles
Crash Handling
11 articles · Page 1 of 1
This technical guide explains the underlying mechanisms of Android crash collection for both Java/Kotlin and native code, outlines a four‑step capture process, compares popular solutions, and provides concrete implementation details—including signal handling, minidump generation, and stack deobfuscation—to help developers reliably record and diagnose app failures.
AndroidCrash HandlingJava
0 likes · 19 min read

Capturing a screenshot right before an Android app crashes provides visual context that speeds reproduction, clarifies UI/UX conditions, saves debugging time, and bridges communication between developers, QA, and support, and this guide shows how to implement it using UncaughtExceptionHandler, ActivityLifecycleCallbacks, PixelCopy, and Kotlin code.
AndroidCrash HandlingKotlin
0 likes · 8 min read

This article details the comprehensive strategies SoulAPP employs across development, gray‑release, and operations to ensure Android app stability, covering R&D reviews, testing automation, crash monitoring, data analysis tools, and runtime safety‑net implementations.
AndroidApp StabilityCrash Handling
0 likes · 14 min read

The article explains how uncaught exceptions cause Electron app crashes on Windows, describes Windows’ user‑mode dump types, shows how Crashpad generates minidumps via a simple exception filter, demonstrates starting the built‑in crash reporter in JavaScript, and outlines uploading and analyzing dumps with Visual Studio or WinDbg, plus a watchdog restart strategy.
Crash HandlingCrashpadDebugging
0 likes · 17 min read

This article explains the iOS system architecture, how Mach and BSD layers handle exceptions, the mechanisms for collecting crashes with KSCrash, strategies for OOM detection and monitoring, and techniques for memory snapshotting and reference‑graph analysis to pinpoint memory bloat.
Crash HandlingKSCrashOOM
0 likes · 21 min read

This article explains the fundamentals of iOS crashes, categorizes common crash types such as wild pointers, deadlocks and watchdogs, presents real-world JD Finance app crash cases with code analysis, and outlines systematic debugging, logging, and preventive practices to keep crash rates well below industry averages.
Crash HandlingMultithreadingiOS
0 likes · 26 min read

The article explains how iOS crash interception must comprehensively and stably capture Mach, exception and signal crashes using combined signal‑and‑exception handlers, details stack‑trace symbolication via Mach‑O image lookup, and outlines safe post‑crash processing with a limited run‑loop while avoiding handler conflicts.
Crash HandlingMach ExceptionSignal
0 likes · 11 min read

NRTripod, NetEase News’ online risk‑control platform, safeguards mobile app stability by tackling third‑party SDK hazards, Android fragmentation, sudden incidents, and hidden development flaws through a four‑layer architecture that combines development‑time debugging tools, production‑time dynamic feature‑flag configuration, real‑time crash interception, SDK toggling via NullObject patterns, and static protections such as whitelists, bytecode processing, and manifest analysis.
AndroidApp StabilityCrash Handling
0 likes · 13 min read

This article introduces the Sunglasses crash investigation tool, explains iOS Objective‑C runtime message handling—including method lookup, dynamic resolution, and forwarding—details method swizzling implementation with code examples, and discusses class clusters and future enhancements for mobile development debugging.
Crash HandlingMethod SwizzlingObjective-C++
0 likes · 14 min read

Bandage is an Android library that intercepts exceptions thrown in activity‑lifecycle callbacks and other main‑thread code via a reflective replacement of ActivityThread’s handler, allowing the app to finish the faulty activity or continue running, with configurable black‑/white‑listing, Bugly integration, and developer‑friendly warnings.
AndroidBandageCrash Handling
0 likes · 11 min read

This article details Ctrip's adoption of React Native, explaining why it was introduced, the framework and tooling built around it, the performance and stability problems encountered, the various bundle‑splitting and engine‑caching solutions applied, and the roadmap for further cross‑platform enhancements.
Bundle SplittingCrash HandlingReact Native
0 likes · 18 min read
