# Avoid suspending panicking thread while crashing \(\#36645\) · gitcafe/zed

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

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

Visibility: public

Requested revision: c5ee3f3e2e51936910f9ad284d14a7974f064616

Requested commit: c5ee3f3e2e51936910f9ad284d14a7974f064616

Commit: c5ee3f3e2e51936910f9ad284d14a7974f064616

Tree: e8e370db594cb0ce7d7afdd20d74efb6fc0ef0e6

Author: Julia Ryan

Committer: GitHub

## Message

```
Avoid suspending panicking thread while crashing (#36645)

On the latest build @maxbrunsfeld got a panic that hung zed. It appeared
that the hang occured after the minidump had been successfully written,
so our theory on what happened is that the `suspend_all_other_threads`
call in the crash handler suspended the panicking thread (due to the
signal from simulate_exception being received on a different thread),
and then when the crash handler returned everything was suspended so the
panic hook never made it to the `process::abort`.

This change makes the crash handler avoid _both_ the current and the
panicking thread which should avoid that scenario.

Release Notes:

- N/A
```

## Parents

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

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