Error when importing svo into the Depth Viewer

Hi,
When I import an svo file into the Depth Viewer, it quickly crashes and gives the following error regardless of the depth mode chosen:

$ ZED_Depth_Viewer
in bool ImageHandler::initialize(sl::Mat&) : Err [999]: unknown error.
Stack trace (most recent call last):
#31 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cbd1cf3, in QCoreApplication::exec()
#30 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cbc975a, in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)
#29 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cc240b7, in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
#28 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fb08ae963c2, in g_main_context_iteration
#27 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fb08aeed6f7, in
#26 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fb08ae98d1a, in g_main_context_dispatch
#25 Object “/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5”, at 0x7fb08762cd6d, in
#24 Object “/lib/x86_64-linux-gnu/libQt5Gui.so.5”, at 0x7fb08cf86a2b, in QWindowSystemInterface::sendWindowSystemEvents(QFlagsQEventLoop::ProcessEventsFlag)
#23 Object “/lib/x86_64-linux-gnu/libQt5Gui.so.5”, at 0x7fb08cfb1306, in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
#22 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cbcae39, in QCoreApplication::notifyInternal2(QObject*, QEvent*)
#21 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d6ba712, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#20 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d719fd4, in
#19 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d716d3f, in
#18 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d6c0e46, in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool)
#17 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cbcae39, in QCoreApplication::notifyInternal2(QObject*, QEvent*)
#16 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d6c2363, in QApplication::notify(QObject*, QEvent*)
#15 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d6ba712, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#14 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d6fd4ed, in QWidget::event(QEvent*)
#13 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d8aed9d, in QToolButton::mouseReleaseEvent(QMouseEvent*)
#12 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d7b21e6, in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
#11 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d7b1fc3, in
#10 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d7b039d, in
#9 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fb08d7b0115, in QAbstractButton::clicked(bool)
#8 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fb08cc027c7, in
#7 Object “ZED_Depth_Viewer”, at 0x56214a38955e, in
#6 Object “ZED_Depth_Viewer”, at 0x56214a38235d, in
#5 Object “ZED_Depth_Viewer”, at 0x56214a381d6d, in
#4 Object “ZED_Depth_Viewer”, at 0x56214a3906e9, in
#3 Object “ZED_Depth_Viewer”, at 0x56214a38edc2, in
#2 Object “ZED_Depth_Viewer”, at 0x56214a3ef275, in
#1 Object “ZED_Depth_Viewer”, at 0x56214a3ac27d, in
#0 Object “/lib/x86_64-linux-gnu/libcuda.so.1”, at 0x7fb09641871f, in
Segmentation fault (Signal sent by the kernel [(nil)])
Segmentation fault (core dumped)

Something like this also happens when I ran ZEDfu:

CUDA Initialisation failed : cudaErrorUnknown
Stack trace (most recent call last):
#22 Object “[0xffffffffffffffff]”, at 0xffffffffffffffff, in
#21 Object “ZEDfu”, at 0x5592a6e007d4, in
#20 Object “/lib/x86_64-linux-gnu/libc.so.6”, at 0x7fcb3a8d9e3f, in __libc_start_main
#19 Object “/lib/x86_64-linux-gnu/libc.so.6”, at 0x7fcb3a8d9d8f, in
#18 Object “ZEDfu”, at 0x5592a6e0069b, in
#17 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3afc2cf3, in QCoreApplication::exec()
#16 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3afba75a, in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)
#15 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3b0150b7, in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
#14 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fcb394513c2, in g_main_context_iteration
#13 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fcb394a86f7, in
#12 Object “/lib/x86_64-linux-gnu/libglib-2.0.so.0”, at 0x7fcb39453d1a, in g_main_context_dispatch
#11 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3b015a66, in
#10 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3afbef26, in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
#9 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3afbbe39, in QCoreApplication::notifyInternal2(QObject*, QEvent*)
#8 Object “ZEDfu”, at 0x5592a6e02032, in
#7 Object “/lib/x86_64-linux-gnu/libQt5Widgets.so.5”, at 0x7fcb3baab712, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#6 Object “/lib/x86_64-linux-gnu/libQt5Core.so.5”, at 0x7fcb3afe941d, in QObject::event(QEvent*)
#5 Object “ZEDfu”, at 0x5592a6e24edc, in
#4 Object “/usr/local/cuda/lib64/libcudart.so.11.0”, at 0x7fcb3c066387, in cudaMemcpy2DToArray
#3 Object “/usr/local/cuda/lib64/libcudart.so.11.0”, at 0x7fcb3c01816c, in
#2 Object “/usr/local/cuda/lib64/libcudart.so.11.0”, at 0x7fcb3c043163, in
#1 Object “/usr/local/cuda/lib64/libcudart.so.11.0”, at 0x7fcb3c041234, in
#0 Object “/lib/x86_64-linux-gnu/libcuda.so.1”, at 0x7fcb3c6b3045, in
Segmentation fault (Address not mapped to object [0x20])
Segmentation fault (core dumped)

The environment is Ubuntu 22.04, the cuda version is 11.7, and the SDK is 3.8. The GPU is RTX 3070.

Please note that when I run an object detection code using the SDK. In addition, The other software packages like ZED Viewer run correctly.

Could you please let me know how I can fix it?

Thank you

Ok, I figured out what was causing this error. In NVIDIA settings, the GPU was put on the “one-demand” mode. When I switched the “performance” mode, both the software packages worked correctly.

1 Like