Closed grooverdan closed 6 years ago
Header only (perf script --debug-mode) files cause the same backtrace:
-rw-rw-r-- 1 dan dan 1384 Apr 4 21:01 stacks.mysql-prep.2018-04-04 21:01:35-05:00 -rw-rw-r-- 1 dan dan 1384 Apr 4 21:01 stacks.mysql-prep.2018-04-04 21:01:58-05:00
Yes, the UI should say "empty file" or something, instead of crashing. Needs to be fixed.
I've got the same issue on all perf files generated from jvm applications. Here's an example: perf-54606.data.gz
@brendangregg can you check this example file? I'll also add a another issue to track general file error handling.
Im getting the same error, perf file was generated using https://github.com/jvm-profiling-tools/async-profiler and the cmd I used was: ./profiler.sh -d 30 -o collapsed -f /tmp/traces.txt 30497
the file is not empty (~10mb)
@rogerwelin async-profiler with -o collapsed
aggregates all the samples into counts per stack trace. flamescope needs each individual sample with a timestamp so it can generate the heatmap over time and flamegraph for a certain time range. I have opened a new feature request in async-profiler for this.
@smarter did you produce perf script
output file from the raw perf.data
file? If not you'll need to.
@grooverdan File handling improvements will be tracked on https://github.com/Netflix/flamescope/issues/18
@rogerwelin @smarter these seem to be invalid files. Let me know if otherwise and I'll reopen the issue.
@ceeaspb Thanks for the help on this!
@ceeaspb can you please elaborate on :
@smarter did you produce
perf script
output file from the rawperf.data
file? If not you'll need to.
I have the same issue.
Ended up being caused by an empty file: -rw-rw-r-- 1 dan dan 0 Apr 4 20:30 stacks.mysql-64-oltp_read_only_1.2018-04-04 20:30:08-05:00