# crashes: Abort after reporting Windows panics \(\#63157\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/fa8d0b7751afc847c5c435691b5fbd91ca9c945f)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: fa8d0b7751afc847c5c435691b5fbd91ca9c945f

Requested commit: fa8d0b7751afc847c5c435691b5fbd91ca9c945f

Commit: fa8d0b7751afc847c5c435691b5fbd91ca9c945f

Tree: ba38fc7ab295346251c0f0a700276f729a118424

Author: Lukas Wirth

Committer: GitHub

## Message

```
crashes: Abort after reporting Windows panics (#63157)

On Windows, the panic hook generated a minidump by calling
`simulate_exception`, but that function only invokes the crash callback
and then returns. Rust could therefore unwind a panicking background
thread while leaving the rest of the application running.

Abort unconditionally after minidump generation, matching the existing
Linux and macOS behavior. The Windows-specific simulation still runs
first so the crash sidecar can persist the exception context and panic
metadata before the process terminates.

Testing:

- `cargo fmt -p crashes --check`
- `cargo nextest run -p crashes`

Release Notes:

- Fixed Windows processes remaining alive after a background thread
panic.
```

## Parents

- [797e5dc95c3859f7926681c91398c4d9e993865d](https://git.cafe/gitcafe/zed/commit/797e5dc95c3859f7926681c91398c4d9e993865d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/fa8d0b7751afc847c5c435691b5fbd91ca9c945f?format=markdown)