Fix panicking on another scope (#6524)
# Objective Fix #6453. ## Solution Use the solution mentioned in the issue by catching the unwind and dropping the error. Wrap the `executor.try_tick` calls with `std::catch::unwind`. Ideally this would be moved outside of the hot loop, but the mut ref to the `spawned` future is not `UnwindSafe`. This PR only addresses the bug, we can address the perf issues (should there be any) later.
This commit is contained in:
parent
15ea93a348
commit
210979f631
@ -299,8 +299,11 @@ impl TaskPool {
|
|||||||
break result;
|
break result;
|
||||||
};
|
};
|
||||||
|
|
||||||
self.executor.try_tick();
|
std::panic::catch_unwind(|| {
|
||||||
task_scope_executor.try_tick();
|
executor.try_tick();
|
||||||
|
task_scope_executor.try_tick();
|
||||||
|
})
|
||||||
|
.ok();
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|||||||
@ -318,10 +318,7 @@ mod test {
|
|||||||
let mut temp = World::new();
|
let mut temp = World::new();
|
||||||
let mut app = App::new();
|
let mut app = App::new();
|
||||||
|
|
||||||
// FIXME: Parallel executors seem to have some odd interaction with the other
|
app.add_system(transform_propagate_system);
|
||||||
// tests in this crate. Using single_threaded until a root cause can be found.
|
|
||||||
app.add_stage("single", SystemStage::single_threaded())
|
|
||||||
.add_system_to_stage("single", transform_propagate_system);
|
|
||||||
|
|
||||||
fn setup_world(world: &mut World) -> (Entity, Entity) {
|
fn setup_world(world: &mut World) -> (Entity, Entity) {
|
||||||
let mut grandchild = Entity::from_raw(0);
|
let mut grandchild = Entity::from_raw(0);
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user