thread 'main' panicked at 'assertion failed: min <= max'

[Danvil]

I get an error after upgrading to the latest version 0.21:

thread 'main' panicked at 'assertion failed: min <= max', /rustc/39c6804b92aa202369e402525cee329556bc1db0\library\core\src\cmp.rs:843:9
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/39c6804b92aa202369e402525cee329556bc1db0/library\std\src\panicking.rs:578
   1: core::panicking::panic_fmt
             at /rustc/39c6804b92aa202369e402525cee329556bc1db0/library\core\src\panicking.rs:67
   2: core::panicking::panic
             at /rustc/39c6804b92aa202369e402525cee329556bc1db0/library\core\src\panicking.rs:117
   3: puffin_imgui::ui::ProfilerUi::ui
   4: imgui::window::Window<Label>::build
   5: puffin_imgui::ui::ProfilerUi::window

Here are the relevant crate versions:

imgui = { version = "0.10", features = ["tables-api"] }
imgui-wgpu = "0.22"
imgui-winit-support = { version = "0.10"  }
puffin = "0.15"
puffin-imgui = "0.21"
wgpu = "0.15"
wgpu-types = "0.15"
winit = "0.27"

[Danvil]

Specifically it happens when I expand the "Frames" header in the GUI when profiling was not turned on previously. If I first turn on profiling programmatically or in the GUI, then it does not happen.