You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
While working on the input port in #176, I set up a test which seems to crash during shutdown -- without using the port I've been working on. I thought it was the port, I finally disabled every bit of it except the constructors, then I removed the use of the new port altogether and it still hangs. CTRL+C still exits but I can't run my test program after that without rebooting.
The pipeline is below in case you want to take a look -- splitter, ISP resizer to h.264 to video stream capture, and no resizer on the other splitter out, just h.264 to video stream capture. Camera is in mode 2 (1920 x 1080). Maybe it's more config restrictions I'm messing up, I don't know. The end of the log where it hangs is also below -- it's usually that exact point, disconnecting ISP from the encoder (or whatever comes next), but not always -- I suspect due to a race condition and the log output doesn't always make it to storage.
While working on the input port in #176, I set up a test which seems to crash during shutdown -- without using the port I've been working on. I thought it was the port, I finally disabled every bit of it except the constructors, then I removed the use of the new port altogether and it still hangs. CTRL+C still exits but I can't run my test program after that without rebooting.
The pipeline is below in case you want to take a look -- splitter, ISP resizer to h.264 to video stream capture, and no resizer on the other splitter out, just h.264 to video stream capture. Camera is in mode 2 (1920 x 1080). Maybe it's more config restrictions I'm messing up, I don't know. The end of the log where it hangs is also below -- it's usually that exact point, disconnecting ISP from the encoder (or whatever comes next), but not always -- I suspect due to a race condition and the log output doesn't always make it to storage.
The text was updated successfully, but these errors were encountered: