Describe the bug
When Aminal is running with -debug option, on each resize of the window, the following messages appearing in the log:
2019-01-16T21:34:03.331+0700 INFO gui/gui.go:531 GL debug message: Error has been generated. GL error GL_INVALID_OPERATION in (null): (ID: 173538523) Generic error
2019-01-16T21:34:03.331+0700 INFO gui/gui.go:531 GL debug message: Error has been generated. GL error GL_INVALID_OPERATION in (null): (ID: 173538523) Generic error
2019-01-16T21:34:03.344+0700 INFO gui/gui.go:531 GL debug message: Error has been generated. GL error GL_INVALID_OPERATION in (null): (ID: 173538523) Generic error
2019-01-16T21:34:03.344+0700 INFO gui/gui.go:531 GL debug message: Error has been generated. GL error GL_INVALID_OPERATION in (null): (ID: 173538523) Generic error
To Reproduce
Steps to reproduce the behavior:
Run Aminal with -debug option
Try to resize the window
See the error messages in the log
Environment (please complete the following information):
OS Windows
Additional context
I'm suspecting that this may lead to leaks of OpenGL memory
When testing on my Debian Stretch VM, there is no such a message
These error messages caused by calls to gl.DisableVertexAttribArray() in glfont/truetype.go, lines 56 and 61. Commenting out those calls eliminates the error messages.
Describe the bug When Aminal is running with
-debug
option, on each resize of the window, the following messages appearing in the log:To Reproduce Steps to reproduce the behavior:
-debug
optionEnvironment (please complete the following information):
Windows
Additional context
gl.DisableVertexAttribArray()
inglfont/truetype.go
, lines 56 and 61. Commenting out those calls eliminates the error messages.But there is a call to
gl.BindVertexArray()
.So this bug seems strange and needs investigation...