Indeed, `noproc` is still possible. The full spec of the exit that was being caught before was `{noproc, {gen_fsm, sync_send_event, Args}}`. The new code still catches that `noproc` as well as other exit reasons now.