This has been an issue in the original @segross version already - enabling IM_ASSERT will flag an assert on shutdown because 1. it tries to destroy the module before clearing out the contexts, and 2. because the context proxy tick works on an "end frame first, begin new immediately" logic, there's never a final end frame before destruction.
This has been an issue in the original @segross version already - enabling IM_ASSERT will flag an assert on shutdown because 1. it tries to destroy the module before clearing out the contexts, and 2. because the context proxy tick works on an "end frame first, begin new immediately" logic, there's never a final end frame before destruction.