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

Access violation exception when resizing image visualizer canvas #913

Closed
glopesdev opened this issue May 28, 2022 · 1 comment
Closed

Access violation exception when resizing image visualizer canvas #913

glopesdev opened this issue May 28, 2022 · 1 comment

Comments

@glopesdev
Copy link
Member

A strange behavior has been observed in specific OS / GPU vendor combinations where resizing an OpenGL framebuffer by resizing the container window will cause a hard crash during the call to SwapBuffers.

Although the cause is unknown, and seems to be down to specific issues with drivers and/or software configuration, a possible workaround is to scale the control along only one axis at a time, as documented elsewhere: ocornut/imgui#3321

Although not performance critical, and technically not a critical blocker for everyone, it will noticeably and dramatically affect systems who suffer from this specific configuration, so any mitigation measures which do not harm existing behavior will be appreciated.

@glopesdev glopesdev added the bug Something isn't working label May 28, 2022
@glopesdev glopesdev added this to the 2.7.0 milestone May 28, 2022
glopesdev added a commit to glopesdev/bonsai that referenced this issue May 29, 2022
@glopesdev
Copy link
Member Author

It appears that the issue was indeed caused by having one instance of Nahimic running in the background as discussed in ocornut/imgui#3321 and ocornut/imgui#5354.

The fix PR reduces the probability of occurrence but does not completely eliminate it if this service is present and running.

If anyone else hits upon this, it's highly recommended to thoroughly check background processes and services for Nahimic and other malware/bloat-ware mentioned in the above issues.

@glopesdev glopesdev removed the bug Something isn't working label Jun 4, 2022
@glopesdev glopesdev removed this from the 2.7.0 milestone Jun 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant