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
cv2.imshow() complains with: error: (-215:Assertion failed) dst.data == (uchar*)dst_ptr in function 'cvShowImage' #167
Comments
The issue was closed in the upstream because the bug was fixed after 4.0.0 release which means that the fix is included in version 4.0.1. This means that I have to make a release which matches OpenCV 4.0.1. |
@skvark any timeline to release the 4.0.1 version? |
After this PR has been merged (if everything goes fine): #182 Probably later this week given that I have enough free time. |
@skvark the 4.0.1 version have released now? |
There is 4.0.1.23 release in PyPI but there were issues with macOS deployment (and with Linux too but that was fixed) so the macOS wheels are missing. I'm about to create a new release which contains also macOS wheels. There will be also 4.1.0 release just after that since it was released yesterday (https://github.com/opencv/opencv/wiki/ChangeLog#version410). |
I have this issue with version 4.1.0 (windows). Any thoughts? |
Please report the issue to upstream repo: https://github.com/opencv/opencv/issues. I cannot fix OpenCV bugs here. I think they fixed the bug with Qt & GTK backends, but Windows wheels shipped by this repo use the native Windows backend and it seems to have been only partially fixed: opencv/opencv#13235 |
thanks! |
Expected behaviour
I was expecting that cv2.imshow() will show the depth image red from openni2 device.
Actual behaviour
When it reaches cv2.imshow("image", img) it crashes with:
This seems to be related to this opencv issue which unfortunately got closed. I don't see why.
This is my related post on stackoverflow:
The shape of img is a tuple (480, 640, 3) and dtype is uint16 just before the call to cv2.imshow()
Please note: The same happens when calling
cv2.imshow("test", np.ones((50, 50), dtype=np.uint16));
... so I guess OpenNI can be ruled out... also downgrading to the latest 3.x release (opencv-python 3.4.5.20) made it work!
Steps to reproduce
The text was updated successfully, but these errors were encountered: