Nsys profiler - wrong event order


I got a “wrong event order” error when running nsys profiler on linux terminal.

Here’s my command:

nsys profile python raven/main_nvsa_marg.py --mode test … (a bunch of run options)

Here’s my error text:

Generating ‘/tmp/nsys-report-bc36.qdstrm’
[1/1] [======34% ] report1.nsys-rep
Importer error status: Importation failed.
Import Failed with unexpected exception: /dvs/p4/build/sw/devtools/Agora/Rel/QuadD_Main/QuadD/Host/QdstrmImporter/main.cpp(34): Throw in function {anonymous}::Importer::Importer(const boost::filesystem::path&, const boost::filesystem::path&)
Dynamic exception type: boost::wrapexceptQuadDCommon::RuntimeException
std::exception::what: RuntimeException
[QuadDCommon::tag_message*] = Status: AnalysisFailed
Error {
Type: RuntimeError
SubError {
Type: InvalidArgument
Props {
Items {
Type: OriginalExceptionClass
Value: “N5boost10wrapexceptIN11QuadDCommon24InvalidArgumentExceptionEEE”
Items {
Type: OriginalFile
Value: “/dvs/p4/build/sw/devtools/Agora/Rel/QuadD_Main/QuadD/Host/Analysis/Modules/EventCollection.cpp”
Items {
Type: OriginalLine
Value: “1055”
Items {
Type: OriginalFunction
Value: “void QuadDAnalysis::EventCollection::CheckOrder(QuadDAnalysis::EventCollectionHelper::EventContainer&, const QuadDAnalysis::ConstEvent&) const”
Items {
Type: ErrorText
Value: “Wrong event order has been detected when adding events to the collection:\nnew event ={ StartNs=90567415755 StopNs=90567420233 GlobalId=283116778389059 Event={ TraceProcessEvent=[{ Correlation=27094481 EventClass=0 TextId=1468 ReturnValue=0 },] } Type=48 }\nlast event ={ StartNs=90671527721 StopNs=90671545254 GlobalId=283116778389059 Event={ TraceProcessEvent=[{ Correlation=27124593 EventClass=0 TextId=1468 ReturnValue=0 },] } Type=48 }”

Here’s my system info:

  • NVIDIA Nsight Systems version 2024.1.1.59-241133802077v0
  • Ubuntu 18.04.6 LTS
  • NVIDIA GeForce RTX 2070, CUDA Version: 12.2 (got by “nvidia-smi”)

Note that if I run “nvcc --version” it will show CUDA version as 9.1.85, which doesn’t match nvidia-smi. Not sure if that’s an issue.

Looking forward to your response.



This is a bug that has been fixed in 2024.2, please update nsys.