Isaac - stereo_dummy application run failed


We are trying to use the isaac sdk for our custom stereocam. We have followed the steps mentioned in the Isaac Documentation. We were able to build the application from our PC and sucessfully deploy it to our Jetson Xavier Board and tried running the stereo_dummy sample application. We referred the below two links for this.



While running the, ./apps/samples/stereo_dummy/stereo_dummy command, we get the below error message.

2019-05-25 20:59:03.472 WARNING engine/alice/backend/backend.cpp@141: This application does not have an explicit scheduler configuration. One will be autogenerated to the best of the systems abilities if possible.
2019-05-25 20:59:03.472 WARNING engine/gems/scheduler/scheduler.cpp@327: No default execution groups specified. Attempting to create scheduler configuration for 8 remaining cores. This may be non optimal for the system and application.
2019-05-25 20:59:03.472 INFO    engine/gems/scheduler/scheduler.cpp@280: Scheduler execution groups are:
2019-05-25 20:59:03.472 INFO    engine/gems/scheduler/scheduler.cpp@289: __BlockerGroup__: Cores = [6, 7], Workers = No
2019-05-25 20:59:03.472 INFO    engine/gems/scheduler/scheduler.cpp@289: __WorkerGroup__: Cores = [0, 1, 2, 3, 4, 5], Workers = Yes
2019-05-25 20:59:03.480 INFO    engine/alice/backend/modules.cpp@217: Loaded module 'packages/dummies/': Now has 36 components total
2019-05-25 20:59:03.482 ERROR   engine/alice/backend/modules.cpp@241: viewers: packages/viewers/ undefined symbol: IsaacGatherComponentInfo
2019-05-25 20:59:03.482 PANIC   engine/alice/backend/modules.cpp@243: Could not load all required modules for application
|                            Isaac application terminated unexpectedly                             |
#01 engine/alice/tools/main(+0x42838) [0x5571a97838]
#02 engine/alice/tools/main(+0xb6f80) [0x5571b0bf80]
#03 engine/alice/tools/main(+0xb7288) [0x5571b0c288]
#04 [0x7f9e4c76c0]
#05 /lib/aarch64-linux-gnu/ [0x7f9e0804d8]
double free or corruption (out)

Do anyone have this issue? Are we missing something??

Akash. S

yes i have also same problem ,you find any solution ???

What jetpack version do you have?
Also, it could be that the file got corrupted while sending as well. Does this error happen if you redeploy?
Before sending again, just clean bazel with the following command “bazel clean --expunge”. This removes the entire working tree for this bazel instance.
If you keep getting that error you can analyze the minidump following instructions here: