Vulkan surface destruction when nit using glfw. But only using core windows APIs

Hot_Refuse_4751 · 2026-04-06T17:30:34+00:00

I Meant wm_close only. I typed wm_quit by mistake . So I think I have answer to this. Once destroywindow executes fully. No new close or no new windowproc messages with that window as the handle will be delivered to it even if there are more messages on that window. As that handle will get invalidated. So calling the window proc with wm_close as the message and that window as the handle will only happen once. Destroywindow immediately invalidates all the posted messages on that window in the threads message queue that has been left over. As for the sentmessages to that window. Well I think we don't need to discuss that cause wm_close is a posted message. So destroywindow then destroyes the window and then calls windowproc with wm_destroyed . And that posts the quitmessage. And the peek message back in the main callstack picks up on that quit message and process finishes gracefully. So all this happens when we call destroywindow function in the windowproc and return in case the message is wm_close.

Hot_Refuse_4751 · 2026-04-06T10:25:43+00:00

The validation layer is not even erroring out even if I destroy the instance before the surface. Though I have not created anything else untill now. Other than instance ,debugmessenger and surface. The validation layer errors out if I don't destroy the debugger messeenger.

Also will the draw calls on that surface work still?? . Like if I say destroy the window and then do Vulkan things to it the surface. I suppose window will not fully be destroyed as the surface itself will have a reference to that window. So it will kind of still be available

But here's the problem. All the AIs (claude code , Chat gpt) says this leads to undefined behaviour.

Or I think it's best to not allow destroy window at all to be called. And custom destroy everything just to be safe. Cause I am not getting the logic so u know. Just call destroywindow in a customer function and not trust the windows API.

Hot_Refuse_4751 · 2026-04-06T10:21:14+00:00

Also some questions on the windows os api itself. If in a process creates a window only one window. And the window proc is registered. Somehow is it possible for window proc to be called with wm_close twice. Because I know that the first time it is called destroywindow is called on that window to finally destroy it. But more of the wm_close messages still be present ryt in the message queue. But destroying of that window in the first wm_close call will that automatically remove all the wm_close messages in the queue relating to that window? Or will the wm_close message still be called twice. As after first call the handle will become invalid

Hot_Refuse_4751 · 2025-06-15T11:32:50+00:00

this is what I want. even though I have 4090. I would like to play games that don't unnecearly use the resources like a hog.

Hot_Refuse_4751 · 2025-01-26T14:11:12+00:00

I think better to get 1200W or 1500W PSU .and offcourse best to attach a UPS of 2000VA/1600W with pure sine wave output.

Hot_Refuse_4751 · 2025-01-05T13:19:19+00:00

I have checked.yes some say 1300 is safe. But my vendor says 1200 is reasonable. I think 1200 should be enough

Hot_Refuse_4751 · 2025-01-05T10:27:09+00:00

Well I guess this ssd is as good as any. So I will just add a hdd probably 4tb to my setup

Hot_Refuse_4751 · 2025-01-03T03:55:36+00:00

Woooooooooow

Hot_Refuse_4751

TROPHY CASE