-
Notifications
You must be signed in to change notification settings - Fork 5k
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
crash while runing desktop/example/hand_tracking #865
Comments
Hi, based on your logs:
I see two issues
While # 2 can be fixed by supplying a path to a video file , the # 1 issue is a deal breaker. You can try using the CPU version of the hand demo, and supply a video path (instead of defaulting to webcam) via -- |
Hi mcclanahoochie, thanks for ur reply, #2 has been fixed now with your help, but for #1, I still get some questions, hope you can help.
Q2. The card of My physical machine is Intel(R)HD Graphics 530, which should support OpenGL ES3.1+, but on my virtual machine it‘s SVGA3D,so could I configure the virtual one as same as my physical one with the purpose of making mediapipe run perfectly on my ubuntu. thanks again, hope you can help here. |
Hi, unfortunately this looks like an issue with how the virtual machine handles the GPU. I would search around for VMware GPU support, or see if you can dual boot into linux. |
Sorry this isn't an answer to your issue, but can you please let me know how you're running the desktop hand_tracking example? I have compiled the example using the command:
The compilation was successful, but I don't know how to actually run the compiled target file / where that file is. Can you please let me know how you ran the example? Thanks. |
@AlexYiningLiu look at the very first post, at the first line that starts with |
closing due to lack of activity |
hand tracking will crash each time in runing with a double free issue, it seems there's something wrong with some kind of resource, BTW, my device is not equiped with webcam, so is it possible caused by no input stream?
The text was updated successfully, but these errors were encountered: