#296 closed defect (fixed)
Redraw errors with opengl enabled on win 7 64 - nvidia gtx 670
Reported by: | aradtech | Owned by: | aradtech |
---|---|---|---|
Priority: | major | Milestone: | 0.9 |
Component: | client | Version: | trunk |
Keywords: | opengl | Cc: |
Description (last modified by )
I was re-sizing the client window when I got this anomaly and the error message beside it that kept going over and over.
Traceback (most recent call last): File "xpra\gl\gl_window_backing.pyc", line 171, in do_gl_paint File "xpra\gl\gl_window_backing.pyc", line 227, in update_texture_yuv File "latebind.pyx", line 32, in OpenGL_accelerate.latebind.LateBind.__call__ (src\latebind.c:768) File "wrapper.pyx", line 315, in OpenGL_accelerate.wrapper.Wrapper.__call__ (s rc\wrapper.c:5933) GLError: GLError( err = 1281, description = 'invalid value', baseOperation = glTexSubImage2D, pyArgs = ( GL_TEXTURE_RECTANGLE_ARB, 0, 0, 0, 586, 615, GL_LUMINANCE, GL_UNSIGNED_BYTE, "\x95\x95\x95\x95\x95\x95\x95\x96\x93..., ), cArgs = ( GL_TEXTURE_RECTANGLE_ARB, 0, 0, 0, 586, 615, GL_LUMINANCE, GL_UNSIGNED_BYTE, "\x95\x95\x95\x95\x95\x95\x95\x96\x93..., ), cArguments = ( GL_TEXTURE_RECTANGLE_ARB, 0, 0, 0, 586, 615, GL_LUMINANCE, GL_UNSIGNED_BYTE, "\x95\x95\x95\x95\x95\x95\x95\x96\x93..., )
I have attached screenshots of said anomaly.
Other behaviors noted with it.
- 1 Re-sizing the image didn't remove the bottom part if I moved it sideways or up ,but not above the line.
- 2 soon as it went above the top line when I pulled it down the issue had gone away and the error message stopped.
Machine specs
Intel I5-3350P
16 gig ram
Nvidia GTX 670
2 monitors attached.
Win 7 64 up to date with all patches.
Attachments (7)
Change History (16)
Changed 8 years ago by
Changed 8 years ago by
Problem Image 2 showing version and other options
Changed 8 years ago by
Problem Image 3 showing more features and videoCard used
Changed 8 years ago by
Problem Image 7 showing fixed after I moved the frame above the blue line.
comment:1 Changed 8 years ago by
Please scroll to the bottom of wiki/Debugging and get an Apitrace of the problem (if you can reproduce it).
If you can't, I'm not sure what to do, I think it's likely to be a race condition.
comment:2 Changed 8 years ago by
Description: | modified (diff) |
---|---|
Owner: | set to Antoine Martin |
Status: | new → accepted |
fix bug formatting
comment:3 Changed 8 years ago by
Owner: | changed from Antoine Martin to aradtech |
---|---|
Status: | accepted → assigned |
aradtech, please see comment:1
comment:4 Changed 8 years ago by
Please reproduce and post the command output with this env var set
XPRA_OPENGL_DEBUG=1
Also please specify if this can be reproduced on this setup only (the machine hardware details, some of which is in the bug title) or if the setup is irrelevant (in which case edit the bug title to reflect that).
comment:5 Changed 8 years ago by
Unable to reproduce at all , its a random issue when using opengl. I get no issues at all like that when not using opengl.
comment:8 Changed 8 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:9 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/296
Problem Image 1