[Caused by buggy software Nahimic] Viewport causing crash with resize in example_glfw_opengl3 + possible memory leak

[dgm3333]

Using the latest docker branch (downloaded this morning although same error on older ones)
Randomly on resizing a child viewport window which is outside the bounds of the main window it crashes the program.

Using win10, 4k dual monitors
CPU: AMD Ryzen 9
GPU: AMD Radeon RX 5700 XT

To replicate
compile a vanilla version of example_glfw_opengl3
(either Release or Debug as happens with both)
As per pic below: Drag the child somewhere outside the boundary of the main window (I haven't managed to get it to to crash while borders of the child remain inside the boundary of the main window)
Grab the "Dear ImGui Demo" or "Hello, world!" window resize triangle (bottom RHS) and just drag it around for a while
At some point after a second or so it crashes (I haven't giffed as it literally just stops)...

Also possible memory leak:
If I repeatedly drag the child out of the main window and drop it then back in and drop it I get this memory consumption (each step up is a new drop outside of the main - but the memory doesn't seem to be released when the window is dropped back inside the main)
If I stop dragging and dropping it then it settles but not by much

These are the screens of the main drag and drop crash:-

[ocornut]

Hello,
could you update to latest now (7b5a8e4) and see if it is fixed?
Merged a change for #4468, #3381, #2981, #4825, #4832, #5127 which wasn't in Docking branch yet.

[dgm3333]

Sorry but it doesn't seem to have worked
The identical action (dragging and dropping Hello, World! in and out) still has a large memory consumption profile (which even beyond a minute of leaving it running with the child sitting in the main window is never released), and it still crashes on resizing (this doesn't have to be released between resizes to trigger - just literally move the child just outside the main and start dragging the resize triangle around). Incidentally although I did them sequentially in this trial the resizing crash will occur without the dragging and dropping first.

Dragging and dropping memory leak (zoom of below)

Resizing crash

[ocornut]

Could you confirm which of the two rendering path is being used, and if using the other works better on your setup? Also please uncomment the debug line that prints vendor, renderer info etc. To share the results here. Thank you!

[rokups]

Crash happens in atio6axx.dll, this DLL comes with AMD graphics driver. Similar crash is reported here (suggests uninstalling "AMD Adrenalin Software"). In general "atio6axx.dll crash" query on a search engine returns plenty of results. Looks like AMD software is quite buggy. See if you can disable any invasive features in Radeon Software (any kind of overlays and similar).

[ocornut]

The crash from that callstack happens because of NAHIMIC which is a broken and unmaintained AUDIO software which somehows manages to mess up with OpenGL.

I don't think it would be reasonable for us to ignore possible issues with AMD or NVIDIA drivers, but Nahimic is simply broken:
See #3204 and #3321

Can you uninstall Nahimic and see how it goes? (may fix the crash but not the memory use?)

[dgm3333]

Woah, I don't think I've ever seen so many expletives in such close proximity to ANY word on the internet as nahimic - any systemware where "malware" is one of the NICE things that people say about it has got to raise questions...
So I'm not even going to ask what the heck a piece of audio software is doing jamming itself into a graphics process...
Anyway it doesn't have an uinnstall option, so after killing the 6 running instances (2x64bit, 2x32 bit and a couple of services.) And deleting as many files as windows administrator priviledges would allow me to remove (not all of them :-( ) I tried again.

Memory consumption is now less than the previous baseline and DROPS (!!!) with resizing and drag/dropping.
I couldn't get the example to crash either...
So I think your piece of s*** comment (now mysteriously vanished) is pretty appropriate...
[sadly various sites say that Nahimic keeps reinstalling itself so I might have to find an anti-nahimic service to keep it off my computer]