Skip to content
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

WaveformArea's sometimes get corrupted with GL_INVALID_OPERATION when the adjacent WaveformArea is moved #41

Closed
azonenberg opened this issue May 2, 2019 · 0 comments
Labels
bug Something isn't working rendering Changes to display capabilities ui New UI features

Comments

@azonenberg
Copy link
Collaborator

Fairly frequently, but not 100% of the time, when a waveform is moved to another viewport a waveform in the original viewport (not the one being moved) stops displaying correctly and the console is spammed with OpenGL error 502 (GL_INVALID_OPERATION).

No steps to trigger the issue reliably on cue are known, however if you keep moving waveforms between views it will eventually show up. All recently observed incidents corrupted the bottom waveform in the original viewport, however it is not known if this is always the case.

Corrupted waveforms can be restored by moving them to another viewport, then (optionally) back to their original location.

@azonenberg azonenberg added bug Something isn't working rendering Changes to display capabilities ui New UI features labels May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working rendering Changes to display capabilities ui New UI features
Projects
None yet
Development

No branches or pull requests

1 participant