a634ce37a6
# Objective Fix #8936. ## Solution Stop using `unwrap` in the core pipelined rendering logic flow. Separately also scoped the `sub app` span to just running the render app instead of including the blocking send. Current unknowns: should we use `std::panic::catch_unwind` around running the render app? Other engine threads use it defensively, but we're letting it bubble up here, and a user-created panic could cause a deadlock if it kills the thread. --- ## Changelog Fixed: Pipelined rendering should no longer have spurious panics upon app exit. |
||
|---|---|---|
| .. | ||
| macros | ||
| src | ||
| Cargo.toml | ||