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

Multi-viewport memory leak with GLFW/OpenGL3 on W10 #6041

Closed
altaitai opened this issue Jan 3, 2023 · 2 comments
Closed

Multi-viewport memory leak with GLFW/OpenGL3 on W10 #6041

altaitai opened this issue Jan 3, 2023 · 2 comments

Comments

@altaitai
Copy link

altaitai commented Jan 3, 2023

Version/Branch of Dear ImGui:

Version: 1.89.2 WIP (18916)
Branch: docking

Back-end/Renderer/Compiler/OS

Back-ends: imgui_impl_glfw.cpp + imgui_impl_opengl3.cpp
Compiler: VS2019 SDK 10.0 (v142)
Operating System: Windows 10

My Issue/Question:

I noticed a memory leak on the stack when running the multi-viewport branch in my project. It's currently reproducible in the example_glfw_opengl3 project in the official VS solution. The leak happens in ImGui_ImplOpenGL3_RenderDrawData and ImGui::RenderPlatformWindowsDefault specifically when we move a window outside of the main viewport. When the window is moved in, the leak stops and the memory usage comes back to the idle state.

Screenshots/Video

2023-01-03_14-22-13

Standalone, minimal, complete and verifiable example:

GLFW/OpenGL3 Example

@ocornut
Copy link
Owner

ocornut commented Jan 3, 2023

We've circled around this forever and it seems to be a bug in Intel GPU drivers that apparently was fixed last year?

@altaitai
Copy link
Author

altaitai commented Jan 3, 2023

We've circled around this forever and it seems to be a bug in Intel GPU drivers that apparently was fixed last year?

Thanks for the quick reply, this is most likely the issue. Drivers on the test machine are outdated (January 2021) and I cannot update them, but fortunately I was able to re-test on another GPU which worked fine. Closing as a duplicate of the mentioned issue.

@altaitai altaitai closed this as completed Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants