Jakob Hellermann

Thanks :) I've addressed the comments (in the other PR as well).

Yea I suppose it would be nice to detect this somehow. Unfortunately I can't think of a way off the top of my head that wouldn't be invasive or do...

That's definitely an unintended regression, `bevy_render` is [meant to be](https://github.com/jakobhellermann/bevy-inspector-egui/blob/2e9f7ebe804cd4f78b74c74b4570fedd53948e13/crates/bevy-inspector-egui/Cargo.toml#L57) optional.

See https://github.com/jakobhellermann/bevy-inspector-egui/issues/128 for some related discussion. > I'm open to making every crate optional that can be entirely removed from the dependency tree (so making bevy_asset optional wouldn't make sense)....

I think the problem is that recent bevy_egui versions, you need a camera2d for egui to show. ```rs use bevy::{input::common_conditions::input_toggle_active, prelude::*}; use bevy_inspector_egui::{bevy_egui::EguiPlugin, quick::WorldInspectorPlugin}; fn main() { App::new() .add_plugins(( DefaultPlugins,...

> Oh, is it that we keep going if we see an unknown subcommand, trying to recover on a failure which in this case will instead flood the user with...

I suppose there are two questions - why does the stack even grow here? - why doesn't libtas handle that correctly during restore

Crash is also fixed by ```c struct rlimit rl; rl.rlim_cur = 16 * 1024 * 1024; setrlimit(RLIMIT_STACK, &rl) != 0); ``` in `Stack::grow`. (I still get the hang)