-
-
Notifications
You must be signed in to change notification settings - Fork 16.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
'cap' object is not self. initialized #1781
Comments
Hello @rohandubey, thank you for your interest in 🚀 YOLOv5! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution. If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you. If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available. For business inquiries or professional support requests please visit https://www.ultralytics.com or email Glenn Jocher at [email protected]. RequirementsPython 3.8 or later with all requirements.txt dependencies installed, including $ pip install -r requirements.txt EnvironmentsYOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
StatusIf this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), testing (test.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit. |
@rohandubey LoadStreams initiates one or more more daemon threads for multi-source streaming. The cv2 cap objects are inside each thread, they are not properties of the dataloader as you note. |
@glenn-jocher The opening and closing of cv2 cap object is governed by the dataloader class, and currently it doesn't release the camera as "cap" is not exclusively defined inside, thus not freeing up the camera pointer. |
🐛 Bug
cap.release() function should be embedded in utils.dataset as closing of a webcam will governed by utils.dataset not detect.py.
But on running utils.dataset, it was throwing off error saying cap is not a a self declared variable in Class LoadStream.
To Reproduce (REQUIRED)
Input:
In utils.dataset() file, class LoadStream:
Output:
Expected behavior
utlis.dataset should effectively be able to release camera.
The text was updated successfully, but these errors were encountered: