A memory leak detection library for Android and Java.
“A small leak will sink a great ship.” - Benjamin Franklin
In your build.gradle:
dependencies {
debugImplementation 'com.squareup.leakcanary:leakcanary-android:1.5.4'
releaseImplementation 'com.squareup.leakcanary:leakcanary-android-no-op:1.5.4'
}In your Application class:
public class ExampleApplication extends Application {
@Override public void onCreate() {
super.onCreate();
if (LeakCanary.isInAnalyzerProcess(this)) {
// This process is dedicated to LeakCanary for heap analysis.
// You should not init your app in this process.
return;
}
LeakCanary.install(this);
// Normal app init code...
}
}You're good to go! LeakCanary will automatically show a notification when an activity memory leak is detected in your debug build.
- Why should I use LeakCanary?
- How do I use it?
- How does it work?
- How do I customize LeakCanary to my needs?
- How do I copy the leak trace?
- How do I fix a memory leak?
- Can a leak be caused by the Android SDK?
- How can I dig beyond the leak trace?
- How do I disable LeakCanary in tests?
- How do I fix build errors?
- How many methods does LeakCanary add?
- Where can I learn more?
- How do I use the SNAPSHOT version?
- How can I be notified of new releases?
- Who's behind LeakCanary?
- Why is it called LeakCanary?
- Who made the logo?
- Build error: Failed to resolve
- Instant Run can trigger invalid leaks
- I know I have a leak. Why doesn't the notification show?
Copyright 2015 Square, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.