Bug when decoding: "duration_complete event must have start tick (166428285) greater than end tick (166428276)"

[Kuinox]

When running ./magic-trace run -working-directory workdir -full-execution -multi-thread ./dotnet/dotnet -- benchmark/Abc.TradingPerfTests.dll

magic-trace end up throwing when writing the trace with the error:
"duration_complete event must have start tick (166428285) greater than end tick (166428276)"

Thanks for helping us make magic-trace better!

Please consider answering any subset of the following questions, based on what you think
is most relevant to your report:

• How can we, magic-trace developers, reproduce the issue you're seeing?

If needed I can provide a zip that contains everything to reproduce the issue.

• What version of perf userspace tools are you running? perf --version

perf version 6.8.12

• What CPU do you have? cat /proc/cpuinfo

Intel(R) Xeon(R) Gold 6146 CPU

[bobjiang82]

Any fix for this bug? I see the same error message.

---

(monitor.ml.Error
(Failure
"duration_complete event must have start tick (4268315) greater than end tick (4021759)")
("Raised at Stdlib.failwith in file "stdlib.ml", line 29, characters 17-33"
"Called from Tracing_zero__Writer.write_duration_complete in file "vendor/tracing/zero/writer.ml", line 354, characters 4-135"
"Called from Tracing__Trace.write_duration_complete.(fun) in file "vendor/tracing/src/trace.ml", line 219, characters 4-46"
"Called from Core__Deque.foldi'.loop in file "core/src/deque.ml", line 91, characters 10-69"
"Called from Core__Deque.foldi' in file "core/src/deque.ml", line 121, characters 10-158"
"Called from Magic_trace_lib__Trace_writer.end_of_thread in file "src/trace_writer.ml", line 604, characters 2-123"
"Called from Async_kernel__Pipe.iter_without_pushback.(fun).loop in file "src/pipe.ml", line 917, characters 10-13"
"Called from Async_kernel__Job_queue.run_jobs in file "src/job_queue.ml", line 180, characters 6-47"
"Caught by monitor Monitor.protect"))

---

perf version 6.12.22

---

CPU: Intel Xeon 6 (GNR)