mirror of
https://github.com/ocornut/imgui.git
synced 2026-11-12 19:14:43 +00:00
High RAM usage while resizing with DX11 #6374
Labels
No labels
accidentally closed
android
backends
bug
building
clipper
coloredit
color spaces
cplusplus
data types
demo
disabled
doc
docking
dpi
drag drop
drawing/drawlist
dropped
dx12
enhancement
focus
font/text
gallery
help wanted
idle/power saving
ime
in progress
inputs
inputtext
internals
label/id and id stack
language bindings
layout
linux/bsd
menus
multi-contexts
multi-threading
multi-viewports
nav
news/info
opengl
optimization
osx/ios
overlap
plot/graph
popups
question
scrolling
selection
settings
sliders/drags
style
tables/columns
tabs
test wanted
tools
tooltips
tree
tricks & tips
useful widgets
vulkan
web
window pos/depth
window sizing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ocornut/imgui#6374
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When resizing the window, the render stops, which is surely normal but when looking in VS to the process memory, after about 10seconds of resizing, it uses up to 20GB of RAM ! I'm using win32 with DX11, the default file.
Dear ImGui 1.89.6 WIP
Version/Branch of Dear ImGui:
Version: 1.19.6
Branch: master
Back-end/Renderer/Compiler/OS
Back-ends: imgui_impl_win32.cpp + imgui_impl_dx11.cpp
Compiler: MSVC
Operating System: Windows 11
My Issue/Question:
Is this normal ?
Screenshots/Video
Standalone, minimal, complete and verifiable example: (see https://github.com/ocornut/imgui/issues/2261)
I saw that the memory was used only when we were changing the size, when we hold the mouse button but don't move, it stays at the point it was before, only when we are currently resizing the window, it goes up very fast. Is there a Vec2 buffer with all the old positions of the window until the button is released ?
This only bugs using DX11; I just tried with DX12 and it does not consume more memory.
I have pushed a workaround for this in
031e152Thanks for reporting!
Well done, it was a bit annoying that it was using that much ram...