- Updates tone to match bug template - Removes the "current vs expected" behavior section - It doesn't feel very useful. Users expect Zed to not crash, regardless of what they are doing. Release Notes: - N/A
44 lines
1.4 KiB
YAML
44 lines
1.4 KiB
YAML
name: Report a crash
|
|
description: Zed is crashing or freezing or hanging.
|
|
type: Crash
|
|
labels: "state:needs triage"
|
|
body:
|
|
- type: textarea
|
|
attributes:
|
|
label: Reproduction steps
|
|
description: A step-by-step description of how to reproduce the crash from a **clean Zed install**. The more context you provide, the easier it is to find and fix the problem fast.
|
|
placeholder: |
|
|
1. Start Zed
|
|
2. Perform an action
|
|
3. Zed crashes
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Zed version and system specs
|
|
description: |
|
|
Open the command palette in Zed, then type “zed: copy system specs into clipboard”.
|
|
placeholder: |
|
|
Zed: v0.215.0 (Zed Nightly bfe141ea79aa4984028934067ba75c48d99136ae)
|
|
OS: macOS 15.1
|
|
Memory: 36 GiB
|
|
Architecture: aarch64
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Attach Zed log file
|
|
description: |
|
|
Open the command palette in Zed, then type `zed: open log` to see the last 1000 lines. Or type `zed: reveal log in file manager` in the command palette to reveal the log file itself.
|
|
value: |
|
|
<details><summary>Zed.log</summary>
|
|
|
|
<!-- Paste your log inside the code block. -->
|
|
```log
|
|
|
|
```
|
|
|
|
</details>
|
|
validations:
|
|
required: false
|