Warp freezes

[jiangnai901]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

After the computer screen goes black, I restart it and directly open Warp, which has processes running but continues to freeze. Reinstalling it doesn't help

To reproduce

The computer screen went black and then forcefully restarted. When I tried to open the Warp terminal again, it froze

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Select an OS

Operating system and version

Windows10

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[oz-for-oss]

@jiangnai901

Here's what I found while triaging this issue:

This is currently underspecified: it appears to be a Windows freeze after a black-screen/forced-restart event, but we need visual evidence and logs to route it confidently. Reinstalling Warp may not clear persisted app state, so a reinstall can leave the same frozen state in place.

I have a few follow-up questions before I can narrow this down:

1. Can you attach a short screen recording or screenshot showing what Warp displays when it freezes after launch?
2. Can you attach the latest redacted Warp logs from a launch that freezes?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that windows freeze after a forced restart/black-screen event is underspecified and needs logs or visual evidence before it can be routed confidently..

Initial triage

This looks like a Windows freeze/hang that occurs when Warp is reopened after the machine hit a black-screen/forced-restart state. The current report does not include enough diagnostic evidence to distinguish between a startup/session-restoration hang, a rendering/GPU initialization problem, or a stale process/single-instance startup path.

Evidence from the report

• Platform detail provided: Windows 10. The OS dropdown was left at Select an OS, but the free-text OS version field says Windows10.
• Symptom: Warp has processes running but the app freezes when opened after the machine went black and was forcefully restarted.
• Reinstalling did not help, which can happen when the triggering state lives in persisted app data/settings rather than the installer bits.
• No Warp version/channel, shell version, logs, screenshots, or screen recording were provided.

Code areas to investigate once logs are available

• app/src/lib.rs initializes Windows single-instance forwarding, settings, crash recovery, and app startup lifecycle callbacks.
• app/src/crash_recovery.rs contains the Windows crash-recovery/GPU-backend fallback paths; it helps with startup crashes but may not explain a hang where the process stays alive.
• app/src/app_services/windows/mod.rs and app/src/app_services/windows/single_instance_manager.rs handle forwarding launches to an existing Windows instance.
• app/src/persistence/sqlite.rs saves/restores persisted app state; persistent state surviving reinstall is relevant if the freeze happens while restoring a prior session.
• crates/warpui/src/rendering/wgpu/mod.rs initializes WGPU and Windows rendering backend options, which is relevant for black-screen/GPU-adjacent startup hangs.

Duplicate check

I enumerated open issues and recently closed issues. #12803 is similar because it is a Windows startup hang after an unclean shutdown, and #14621 is similar because it is a Windows hang after sleep/wake, but the incoming report lacks enough detail to confidently mark it as a duplicate of two or more existing issues under the duplicate-detection threshold.

Current blocker

The next useful step is reporter-provided evidence from a frozen launch so maintainers can tell whether this is session restoration, rendering/GPU, or process/startup forwarding.

Question reasoning

1. Can you attach a short screen recording or screenshot showing what Warp displays when it freezes after launch? — The visible frozen state would help distinguish a startup window/rendering hang from a terminal/session restoration hang.
2. Can you attach the latest redacted Warp logs from a launch that freezes? — Logs are needed to identify whether the freeze occurs during Windows startup forwarding, persisted session restore, GPU initialization, or shell/terminal startup.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[warp-agent-staging]

Oz couldn't complete this task because required inputs, permissions, or resources were invalid or unavailable.

Error Details:
Environment setup failed: Failed to clone warpdotdev-demos/agent-eval-kit, warpdotdev/warp. Check your repository URLs and setup commands.