Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Depthai version 2.14.1 crashes #1149

Closed
Grumpy141 opened this issue Feb 16, 2022 · 4 comments
Closed

Depthai version 2.14.1 crashes #1149

Grumpy141 opened this issue Feb 16, 2022 · 4 comments

Comments

@Grumpy141
Copy link

Depthai crashes the entire JVM while establishing communication to the device. Tested on both Mac OS intel 64bit, and Linux armhf. The crash was the same: (Version 2.13.3. works fine)

Error Mesage On Mac:

Stack trace (most recent call last) in thread 123145447182336:
#2 Object "libsystem_platform.dylib", at 0x7ff8043f5e2c, in _sigtramp + 28
#1 Object "libdepthai-core.dylib", at 0x13941b16d, in backward::SignalHandling::sig_handler(int, __siginfo*, void*) + 13
#0 Object "libdepthai-core.dylib", at 0x13941b1dc, in backward::SignalHandling::sig_handler(int, __siginfo*, void*) + 124

Error Message On Linux armhf:

Stack trace (most recent call last) in thread 27821:
#2 Object "/lib/arm-linux-gnueabihf/libc.so.6", at 0xb6d5f12f, in
#1 Object "/home/pi/.javacpp/cache/depthai-linux-armhf.jar/org/bytedeco/depthai/linux-armhf/libdepthai-core.so", at 0x158a7aef, in backward::SignalHandling::sig_handler(int, siginfo_t*, void*)
#0 Object "/home/pi/.javacpp/cache/depthai-linux-armhf.jar/org/bytedeco/depthai/linux-armhf/libdepthai-core.so", at 0x158a5d17, in backward::SignalHandling::handleSignal(int, siginfo_t*, void*)
Segmentation fault (Address not mapped to object [0x4])

@saudet
Copy link
Member

saudet commented Feb 17, 2022

Let's not create a new thread for this, unless/until we know that we're dealing with a different issue.

@saudet
Copy link
Member

saudet commented Feb 17, 2022

Duplicate of #1118

@saudet saudet marked this as a duplicate of #1118 Feb 17, 2022
@saudet saudet closed this as completed Feb 17, 2022
@Grumpy141
Copy link
Author

Grumpy141 commented Feb 17, 2022 via email

@saudet
Copy link
Member

saudet commented Feb 17, 2022

It could be the same issue, in C/C++ undefined behavior is undefined behavior, which means a bug does not necessarily affect everyone in the same way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants