Open jnak opened 5 years ago
As an alternative strategy, I was able to use v1.0.2 of the chrome2calltree tool to produce a Callgrind file from the py2devtools output, which worked with the QCacheGrind tool installed via Homebrew on a Mac (as noted in the npm package docs; there's also KCacheGrind for Linux, not sure about Windows). The UX is quite different from Chrome, but I was at least able to get some useful data out of my profiles this way.
I'm not able to have the Chrome Dev Tools work a Profile file generated by
py2devtools.py
.I quickly compared the format generated by
py2devtools
and the one generated by Chrome and they seem quite different. The former starts with an object, the latter with an array. Since it looks like the Chrome Dev Tools have been updated recently, I wonder if the format expected has changed.Are you still able to get Chrome to load your profile files?
Thanks, J