00356f96c5
Summary: Previously we used <Link/> everywhere with useBaseUrl to avoid link destinations depending on the current url of the page. This isn't necessary if you instead link to the **file name**, rather than the **url path**. Then the links are resolved at build time, and work across imported markdown files etc. This diff just does the pages under Features, because other ones will get conflicts. I'll do those later. Reviewed By: nikoant Differential Revision: D25589707 fbshipit-source-id: 35ca986e19fc2af1054b81d7253eeb3827947ab8
15 lines
673 B
Plaintext
15 lines
673 B
Plaintext
---
|
|
id: leak-canary-plugin
|
|
title: LeakCanary
|
|
---
|
|
import useBaseUrl from '@docusaurus/useBaseUrl';
|
|
|
|
→ [See setup instructions for the LeakCanary](../setup/leak-canary-plugin.mdx)
|
|
|
|
The LeakCanary plugin provides developers with Flipper support for [LeakCanary](https://github.com/square/leakcanary), an open source memory leak detection library.
|
|
|
|
Leaks detected by LeakCanary will appear automatically in Flipper. Each leak will display a hierarchy of objects, beginning from the garbage collector root and ending at the leaked class.
|
|
Selecting any object in this list will display contents of the object's various fields.
|
|
|
|
Note: this plugin is only available for Android.
|