Summary: Per title. Reviewed By: danielbuechele Differential Revision: D15898614 fbshipit-source-id: b2d86a58e80b1309159bc738bcc66ca09cd796ad
1.9 KiB
1.9 KiB
id, title, sidebar_label
| id | title | sidebar_label |
|---|---|---|
| images-plugin | Images Setup | Images |
Currently, the images plugin only supports Fresco for Android as backend, but just like the network plugin, support for other image loading libraries could easily be added. Send us a PR!
Fresco and Android
import com.facebook.flipper.plugins.fresco.FrescoFlipperPlugin;
client.addPlugin(new FrescoFlipperPlugin());
The FrescoFlipperPlugin constructor offers a whole lot of configuration options which
can be useful if you have an advanced setup of Fresco in your application:
FrescoFlipperPlugin(
DebugImageTracker imageTracker,
PlatformBitmapFactory bitmapFactory,
@Nullable FlipperObjectHelper flipperObjectHelper,
DebugMemoryManager memoryManager,
FlipperPerfLogger perfLogger,
@Nullable FrescoFlipperDebugPrefHelper debugPrefHelper,
@Nullable CloseableReferenceLeakTracker closeableReferenceLeakTracker) { ... }
Leak Tracking
The Flipper plugin can help you track down CloseableReferences who have not had
close() called on them. This can have a negative impact on the performance of
your application.
Do enable this functionality, you need to create a CloseableReferenceLeakTracker
and set it in both your ImagePipelineConfig for Fresco and the FrescoPluginPlugin
on creation.
import com.facebook.imagepipeline.debug.FlipperCloseableReferenceLeakTracker;
// ...
FlipperCloseableReferenceLeakTracker leakTracker = new FlipperCloseableReferenceLeakTracker();
new ImagePipelineConfig.Builder()
// ...
.setCloseableReferenceLeakTracker(leakTracker)
.build();
client.addPlugin(new FrescoFlipperPlugin(
new FlipperImageTracker(),
Fresco.getImagePipelineFactory().getPlatformBitmapFactory(),
null,
new NoOpDebugMemoryManager(),
new NoOpFlipperPerfLogger(),
null,
leakTracker));