question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow access to internal Utils for debugging purposes and improve usage stats.

See original GitHub issue

Is your feature request related to a problem? Please describe. My team is considering migrating from Picasso to Coil. We have had an internal debugging tool with Picasso that allows us to view stats of the Picasso instance, using the Picasso StatsSnapshot object. We would like to keep that functionality, and it looks like some of the same logic is already in this library.

Describe the solution you’d like Cache data appears to be already present in coil.util.Utils but it is marked as internal. Not all of the stats that we use are tracked however. It would useful to have similar snapshot functionality with Coil.

Additional context Here are the stats accessible in StatsSnapshot

  public final int maxSize;
  public final int size;
  public final long cacheHits;
  public final long cacheMisses;
  public final long totalDownloadSize;
  public final long totalOriginalBitmapSize;
  public final long totalTransformedBitmapSize;
  public final long averageDownloadSize;
  public final long averageOriginalBitmapSize;
  public final long averageTransformedBitmapSize;
  public final int downloadCount;
  public final int originalBitmapCount;
  public final int transformedBitmapCount;

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
colinrtwhitecommented, Sep 6, 2020

Closing this as EventListener can be used to build stats tracking functionality.

0reactions
colinrtwhitecommented, May 6, 2020

The approach would be similar to Picasso 3 - provide an EventListener implementation that tracks the stats.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Four Steps for Debugging your Content Delivery on AWS
Four Steps for Debugging your Content Delivery on AWS · Step 1: Enable CloudFront logging · Step 2: Set up alarming · Step...
Read more >
Use dump files in the debugger - Visual Studio (Windows)
To debug kernel-mode dump files or use the SOS.dll debugging extension in Visual Studio, download the debugging tools for Windows in the ...
Read more >
Collect Logs and Debugs from Catalyst 9800 WLC for ...
This document describes steps to collect important debugs or show commands from Catalyst 9800 Wireless LAN Controllers(WLC). To provide this information up ...
Read more >
4. Debugging Techniques - Linux Device Drivers, 3rd ...
This chapter introduces techniques you can use to monitor kernel code and trace errors under such trying circumstances. Debugging Support in the Kernel....
Read more >
Debugging and Profiling
On most UNIX systems you can also use the dmesg command to access the kernel log. ... There are also some tools like...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found