Systems | Development | Analytics | API | Testing

Memory leaks are the bugs that really creep up on you. One minute your app is running perfectly, then suddenly it slows to a crawl or crashes. We don’t get a warning with memory leaks, so we need to prepare proactively and be ready when they hit. This means we need to: This guide is here for all of that.

Remote debugging using IntelliJ IDEA offers several benefits. Using this JetBrains IDE, you get interactive breakpoints, variable inspection, and debugging integrated directly with the IntelliJ editor. However you can also introduce configuration complexity and potential security risks if you don’t get it right. IntelliJ has become a favorite of the Bugfender team and in this post we’ll walk through the full setup, from the JVM flag to debugging inside a Docker container.

An app crash is one of the fastest ways to drain both users and rankings. Many users will uninstall an app after just one crash, and both the App Store and Google Play will penalize crash-prone or unstable apps. At Bugfender, we’ve been investigating app crashes since 2014. In this post we’re going to share all our key learnings, so you can: You’ll come away with a reliable, repeatable way to anticipate app crashes – wherever they happen. This post is generally platform-agnostic.