[fix] Window resize crash#13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix ImGui Assertion Crash on Window Resize
Background & Motivation
Currently, the Loom application crashes with an ImGui assertion failure when the window is resized. The crash occurs because the main loop unconditionally starts an ImGui frame (imgui.beginFrame()), but the Vulkan backend (vulkan.drawFrame()) may abort the render process midway if it detects a window resize or an out-of-date swapchain. This early exit skips the corresponding imgui.endFrame() call, leaving the ImGui state machine unbalanced and triggering an assertion on the next frame.
Proposed Solution
The industry-standard, professional solution is to split the monolithic VulkanContext::drawFrame into two distinct phases: beginFrame() and endFrame().
By attempting to acquire a Vulkan frame before building the UI, the application can gracefully skip generating UI data if the swapchain needs to be recreated. This prevents wasted CPU cycles and ensures the ImGui lifecycle remains perfectly balanced. Exposing the VkCommandBuffer to the main loop also sets a robust architectural foundation for future compute shader dispatches.
Key Files & Context
Implementation Steps
Extract the second half of the old drawFrame logic: