Reproduction steps
I am experiencing an issue where Zed fails to launch the UI window on startup. When creating a new instance, the process appears in my system task manager/monitor, but the window never renders. I have to manually kill the process to try again.
This happened multiple times in a row. Eventually, after killing the process and restarting several times, it managed to start successfully.
Relevant Logs:
I extracted the logs from ~/.local/share/zed/logs/. You can see the process starts, connects to the crash handler, and then immediately begins spamming "hang detected" before the GPU initialization or Window rendering seems to complete.
Comparison with successful start:
When it finally started successfully (at 22:59:22), the logs immediately showed [gpui::platform::blade::blade_renderer] Initializing Blade pipelines and Rendered first frame. These lines are missing from the hung sessions, suggesting the hang happens before the renderer initializes.
Attachments:
/home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-55-00.miniprof
/home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-58-05.miniprof
Zed version and system specs
- OS: Linux (Ubuntu 24.04 based on Mesa version in logs)
- GPU: Intel(R) HD Graphics 4400 (HSW GT2)
- Driver: Intel open-source Mesa driver (Mesa 25.0.7)
- Zed Version: 0.217.4+stable
Attach Zed log file
Zed.log
2026-01-06T22:54:37+01:00 INFO [zed] ========== starting zed version 0.217.4+stable.106.39c2ebc0db1d1436f3e77090261c77bd66056291, sha 39c2ebc ==========
2026-01-06T22:54:49+01:00 INFO [crashes] spawning crash handler process
2026-01-06T22:54:50+01:00 INFO [crashes] crash handler registered
2026-01-06T22:54:55+01:00 INFO [extension_host] extensions updated. loading 5, reloading 0, unloading 0
2026-01-06T22:54:56+01:00 INFO [gpui::platform::linux::platform] activate is not implemented on Linux, ignoring the call
2026-01-06T22:55:00+01:00 INFO [zed::reliability] hang detected, trace file saved at: /home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-55-00.miniprof
2026-01-06T22:55:01+01:00 INFO [zed::reliability] hang detected, trace file saved at: /home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-55-00.miniprof
2026-01-06T22:55:02+01:00 INFO [zed::reliability] hang detected, trace file saved at: /home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-55-00.miniprof
... (Repeated hang detection messages) ...
Reproduction steps
I am experiencing an issue where Zed fails to launch the UI window on startup. When creating a new instance, the process appears in my system task manager/monitor, but the window never renders. I have to manually kill the process to try again.
This happened multiple times in a row. Eventually, after killing the process and restarting several times, it managed to start successfully.
Relevant Logs:
I extracted the logs from
~/.local/share/zed/logs/. You can see the process starts, connects to the crash handler, and then immediately begins spamming "hang detected" before the GPU initialization or Window rendering seems to complete.Comparison with successful start:
When it finally started successfully (at
22:59:22), the logs immediately showed[gpui::platform::blade::blade_renderer] Initializing Blade pipelinesandRendered first frame. These lines are missing from the hung sessions, suggesting the hang happens before the renderer initializes.Attachments:
/home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-55-00.miniprof
/home/winner/.local/share/zed/hang_traces/hang-2026-01-06_22-58-05.miniprof
Zed version and system specs
Attach Zed log file
Zed.log