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

The program keeps crashing/freezing without a warning or error code #34

Open
RemoteCMeijer opened this issue Mar 1, 2024 · 8 comments

Comments

@RemoteCMeijer
Copy link

Whilst using TL, the system keeps crashing/freezing without a warning or error code making it difficult to investigate the issue.
The system was recently updated to Ubuntu 20.04 in the hopes that the issue would be resolved.

When the TL plug-in is not responding when running a scan, we can see by running protonect an entirely black screen. Killing the power of the Kinect, and replugging it, sometimes resolves the issue temporarily.

We are wondering of you know of other users with such issues or that it might be caused by hardware issues. E.g. faulty cables, scanner, or a USB port that is being used.

As to our knowledge no error code or the sorts is given, it is difficult to pin point the issue.

@petrasovaa
Copy link
Member

When you run the Protonect binary by itself, does it work without problems? Running kinect from the plugin together with Protonect is expected to fail.

@RemoteCMeijer
Copy link
Author

@petrasovaa Thank you for your reply. Sorry for my late reply, I only have access to Tangible Landscape on Fridays. Good to know that running TL together with Protonect is bound to go wrong.

Protonect seems to run without problems, indeed.

TL without running protonect regurarely stops responding. When this happens the last line in the terminal just states:
[Info] [Freenect2DeviceImpl] started

@petrasovaa
Copy link
Member

Strange. Try running r.in.kinect directly. Sorry, I can't give you detailed instructions right now...

@RemoteCMeijer
Copy link
Author

RemoteCMeijer commented Mar 22, 2024

Strange. Try running r.in.kinect directly. Sorry, I can't give you detailed instructions right now...

Unfortunately, I did not yet have the opportunity to run r.in.kinect directly.

When you run the Protonect binary by itself, does it work without problems? Running kinect from the plugin together with Protonect is expected to fail.

However, we’ve found that running solely Protonect also crashes...

@RemoteCMeijer
Copy link
Author

RemoteCMeijer commented Mar 22, 2024

r.in.kinect is now running fine for ~25 minutes

And then it just stops, after writing the output several times before

(Fri Mar 22 12:09:32 2024)
r.in.kinect --overwrite output=Kinect_output resolution=0.0021 color_output=Kinect_color vector=Kinect_output_vector draw_threshold=760
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 7 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 @2:5 with serial 022615543847
[Info] [Freenect2Impl] found 1 devices
creating OpenGL processor
[Info] [Freenect2DeviceImpl] opening...
[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 2016384 ir: 60833792
[Info] [Freenect2DeviceImpl] opened
[Info] [Freenect2DeviceImpl] starting...
[Info] [Freenect2DeviceImpl] submitting rgb transfers...
[Info] [Freenect2DeviceImpl] submitting depth transfers...
[Info] [Freenect2DeviceImpl] started
[Info] [DepthPacketStreamParser] 1 packets were lost
WARNING: Vector map <Kinect_output_vector> already exists and will be overwritten
Writing to map ...
Writing colors to RGB maps ...
[Info] [Freenect2DeviceImpl] stopping...
[Info] [Freenect2DeviceImpl] canceling rgb transfers...
[Info] [Freenect2DeviceImpl] canceling depth transfers...
[Info] [Freenect2DeviceImpl] stopped
[Info] [Freenect2DeviceImpl] closing...
[Info] [Freenect2DeviceImpl] releasing usb interfaces...
[Info] [Freenect2DeviceImpl] deallocating usb transfer pools...
[Info] [Freenect2DeviceImpl] closing usb device...
[Info] [Freenect2DeviceImpl] closed
[Info] [Freenect2DeviceImpl] closing...
[Info] [Freenect2DeviceImpl] already closed, doing nothing
(Fri Mar 22 12:09:36 2024) Command finished (3 sec)
(Fri Mar 22 12:09:39 2024)
r.in.kinect --overwrite output=Kinect_output resolution=0.0021 color_output=Kinect_color vector=Kinect_output_vector draw_threshold=760
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 7 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 @2:5 with serial 022615543847
[Info] [Freenect2Impl] found 1 devices
creating OpenGL processor
[Info] [Freenect2DeviceImpl] opening...
[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 20
16384 ir: 60833792
[Info] [Freenect2DeviceImpl] opened
[Info] [Freenect2DeviceImpl] starting...
[Info] [Freenect2DeviceImpl] submitting rgb transfers...
[Info] [Freenect2DeviceImpl] submitting depth transfers...
[Info] [Freenect2DeviceImpl] started

@petrasovaa
Copy link
Member

Strange. Try running r.in.kinect directly. Sorry, I can't give you detailed instructions right now...

Unfortunately, I did not yet have the opportunity to run r.in.kinect directly.

When you run the Protonect binary by itself, does it work without problems? Running kinect from the plugin together with Protonect is expected to fail.

However, we’ve found that running solely Protonect also crashes...

If Protonect crashes by itself, then the issue seems to be with libfreenect2, no? I remember having issues that I was able to resolve by updating/reinstalling graphics drivers, I always had to use the proprietary nvidia drivers, not the open source one. In another similar case, it looked like the problem was in the kinect device itself, we had to replace it.

@RemoteCMeijer
Copy link
Author

RemoteCMeijer commented Apr 12, 2024

We updated the graphics drivers, which also updated the kernel used. The newer kernel was throwing us some problems which we had to resolve.

In the end in the boot menu we disalbed the integrated Video. Now, we use the manually installed driver for the NVIDIA card.

After ~15 mins it crashes again, stuck on scanning, saying "wxgui.py" not responding.

At this point in time, it could indeed be the scanner itself.

@RemoteCMeijer
Copy link
Author

We ran into the problem of the GLSL not being supported, see:
https://stackoverflow.com/questions/52592309/glsl-3-30-is-not-supported-when-compiling-glsl-shader-on-ubuntu-18-04

Today we enabled the grahics card again but could not select any drivers for it, Running the following command to update the drivers: sudo ubuntu-drivers install fixed this issue. See, https://askubuntu.com/questions/1237590/not-able-to-change-the-nvidia-driver-in-ubuntu-20-04

After a while it is still not responding. But in the end it could still be a faulty scanner.

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

No branches or pull requests

2 participants