The reason why is because the Event model now defers closing the loading tab and opening the model editor by one frame, so there's a frame where the LoadingTab calls std::future::get after the future has already been handled. On Windows/Linux, this is fine (it throws an exception along the lines of "missing state"), but on MacOS it segfaults.
Happens after the
Event
refactor.The reason why is because the
Event
model now defers closing the loading tab and opening the model editor by one frame, so there's a frame where theLoadingTab
callsstd::future::get
after the future has already been handled. On Windows/Linux, this is fine (it throws an exception along the lines of "missing state"), but on MacOS it segfaults.