Generating a flame graph creates large files in bin/

[Chubab]

File: CPU_Usage_(Sampled)_Randomascii_Export.csv

I'd expect those files to be created alongside the etwtraces in MyDocuments. Dynamic files in bin/ is unexpected.

This is particularly problematic for me because I sync my etwpackage repo to all my machines across Google Drive (crazy, I know but eh... auto-update :))

[randomascii]

Hmmm. That does sound suboptimal.

I don't actually use that script anymore - I use WPA's flame graph generator as it is more convenient. So that's one option. Or, the script could be fixed. It should be easy but I don't know when I'll get to it. Pull requests always welcome...

[Chubab]

Ah cool, never tried the WPA option, will give it a shot. As for this issue, I assume it has to do with CWD. Le mer. 7 févr. 2018 19 h 02, Bruce Dawson <[email protected]> a écrit :

…

Hmmm. That does sound suboptimal. I don't actually use that script anymore - I use WPA's flame graph generator as it is more convenient. So that's one option. Or, the script could be fixed. It should be easy but I don't know when I'll get to it. Pull requests always welcome... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#116 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKULPBwhpnibYyk9FxZbD0Oy8srPwBOVks5tSeUlgaJpZM4R8fkV> .

[randomascii]

I wrote up some documentation of the WPA flamegraph feature here:

https://randomascii.wordpress.com/2016/09/05/etw-flame-graphs-made-easy/