Image opened from REPL hangs - macOS
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1k
- Avg merge
- 22h 17m
- Merged PRs (30d)
- 3
Description
Expected behaviour
An image opened from a Python shell should close:
- after 1 second with
cv2.waitKey(1000) - with
cv2.destroyWindow("<window_name>") - with
cv2.destroyAllWindows()
Actual behaviour
The image opens, but it hangs when closing in either of the two above cases.
Steps to reproduce
OS: macOS Catalina 10.15.7
opencv-python version - 4.5.5.64
python version: 3.10.4
From within a python shell:
import cv2
img = cv2.imread("<path_to_image>")
cv2.imshow("window", img)
After this, any of the three options listed in the expected behavior will result in a frozen, unresponsive window. I don't think this is expected behavior because I haven't seen anything about this in the docs, but I could be very wrong. Thank you!
Issue submission checklist
- This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)
- I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)
- The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")
- I'm using the latest version of
opencv-python
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the repository README first to confirm whether this package can address GUI behavior or only builds precompiled binaries. Then run the provided Python REPL reproduction on the stated macOS, Python, and opencv-python versions; done means determining whether the problem is in the build or package and, if not, identifying it as an upstream OpenCV issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100