Quick answer: Vulkan validation layer flooding with descriptor-pool-reset warnings? The default flags warn on every reset - filter via VK_EXT_validation_features or scope down with VK_LAYER_KHRONOS_validation messages.

Frame timing is fine, but stderr scrolls so fast you can't see real warnings. Every frame's pool reset generates a stack.

Filter validation severities

VkValidationFeaturesEXT features = {};
features.disabledValidationFeatureCount = 1;
features.pDisabledValidationFeatures =
  &VK_VALIDATION_FEATURE_DISABLE_OBJECT_LIFETIMES_EXT;

Reduces the noise floor. Keep the high-severity messages; drop the per-frame chatter.

Use a logging callback

Filter via your PFN_vkDebugUtilsMessengerCallbackEXT. Suppress messages by ID once you've verified they're benign; never suppress by severity alone.

Pool-per-frame pattern

If you're reset-flooded, consider one descriptor pool per frame-in-flight, free on rotation. Eliminates the resets entirely.

“Validation layers are noisy by design. The signal lives under the noise unless you tune.”

Keep a list of suppressed message IDs in source. When validation reports something new, you'll see it; when it reports the old noise, it's ignored.