Via mellinoe on discord - "What you are talking about sounds like ocornut/imgui#1651"

bryanedds — Today at 12:05 PM
reading over this doc that was linked to from that discussion - https://github.com/ocornut/imgui/wiki/Error-Handling
it looks like I can for the most part simply avoid a runtime crash with this - io.ConfigErrorRecoveryEnableAssert <- false
which i think solves the biggest problem with the issue for the most part
one of the prescribed error recovery patterns doesn't work in .NET, tho -

ImGuiErrorRecoveryState state;
ImGui::ErrorRecoveryStoreState(&state);
try
{
    .... run code
}
catch
{
    ImGui::ErrorRecoveryTryToRecoverState(&state);
}

In .NET, you cannot catch an AccessViolationException or an EngineExecutionException and also
ImGui.NET appears to not provide the API for ErrorRecoveryStoreState
(which may make sense because the above pattern is not implementable anyways)
so the only thing we can really do in .NET is avoid the asserts in the first place
which, i think is fine for now, but still, I think there's utility in having a callback when people want to leave ImGui asserts on.

Removed bug label since this should rarely be an issue due to commit 022a799.