Open jasta opened 9 years ago
@paulirish any chance you have some context on this? In particular, with: https://code.google.com/p/chromium/issues/detail?id=277984#c34?
Seems like a good bug. Can you file a new one? On Mar 13, 2015 2:44 PM, "Josh Guilfoyle" notifications@github.com wrote:
@paulirish https://github.com/paulirish any chance you have some context on this? In particular, with: https://code.google.com/p/chromium/issues/detail?id=277984#c34?
— Reply to this email directly or view it on GitHub https://github.com/facebook/stetho/issues/92#issuecomment-79442606.
Filed upstream as: https://code.google.com/p/chromium/issues/detail?id=467222
Upstream is implementing the required changes, we're back in business! Go Chromium team!
@paulirish any chance you can help out here? The activity on https://code.google.com/p/chromium/issues/detail?id=467222 has mysteriously stalled just shy of having this perfectly wired up for our purposes. The only bug remaining is that allocation stack traces are not recalled from the new .heaptimeline
file format.
Sorry. We've had some activity in the project recently that had delayed our look at this. If you can help me with a patch file I'll get it through code review. On Apr 30, 2015 4:09 PM, "Josh Guilfoyle" notifications@github.com wrote:
@paulirish https://github.com/paulirish any chance you can help out here? The activity on https://code.google.com/p/chromium/issues/detail?id=467222 has mysteriously stalled just shy of having this perfectly wired up for our purposes. The only bug remaining is that allocation stack traces are not recalled from the new .heaptimeline file format.
— Reply to this email directly or view it on GitHub https://github.com/facebook/stetho/issues/92#issuecomment-97996397.
Woohoo! Upstream finished the feature!
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
Bump. We need to keep this alive, though the implementation is seriously delayed due to unforeseen issues in the Dalvik/ART support for allocation profiling.
This may be possible using a private API that powers DDMS' lame Allocation Tracking UI: https://android.googlesource.com/platform/libcore/+/android-5.1.0_r1/dalvik/src/main/java/org/apache/harmony/dalvik/ddmc/DdmVmInternal.java
This API has been stable for a very long time AFAICT (I looked all the way back to Ice Cream Sandwich). I believe it will continue to be stable as well.
The format of the
getRecentAllocations
method is defined by ddmlib: https://android.googlesource.com/platform/tools/base/+/android-5.1.0_r1/ddmlib/src/main/java/com/android/ddmlib/AllocationsParser.javaThe major issue to overcome is the seemingly incomplete
heapsnapshot
file format that Chrome uses. In particular, there's limited UI and file format support for allocation stack traces and the format exported/imported by DevTools appears to even lose the limited information that does currently exist. Upstream discussion started at: https://code.google.com/p/chromium/issues/detail?id=277984#c34