Pre-submit Checks
Describe the bug
I am experiencing a persistent and critical issue with the Warp terminal on my Windows 11 system. The application initially appears to load, but after a few moments, the screen begins to flicker, an NVIDIA notification appears, and the application becomes unresponsive before crashing.
My system specifications are:
Operating System: Windows 11 (fully updated)
GPU: NVIDIA GeForce RTX 4080 (using the latest drivers)
I have performed extensive troubleshooting based on the information in your documentation. The following steps have not resolved the issue:
I have installed the latest GPU drivers.
Running the app with --no-gpu fails to launch it at all.
I have uninstalled and reinstalled Warp completely.
I have confirmed that my antivirus and firewall are not blocking the application.
I have tried the documented workaround using the $env:WGPU_BACKEND="vulkan,gl" flag. This prevented the "not responding" error, but it caused the screen to flicker constantly, making the application unusable.
Upon reviewing the Windows Event Viewer logs, I have identified a critical detail. The warp.exe error (Application Hang) occurs at the exact same time as an Application Error for pwsh.exe (PowerShell). This suggests that the issue is not just in Warp's rendering, but in a specific conflict that arises when Warp attempts to render the PowerShell shell using my GPU's drivers.
This interaction appears to be the root cause of the crash. I have included the relevant log entries below for your review.
To reproduce
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Windows
Operating system and version
windows 11
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?
Yes, this issue prevents me from using Warp daily.
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
Pre-submit Checks
Describe the bug
I am experiencing a persistent and critical issue with the Warp terminal on my Windows 11 system. The application initially appears to load, but after a few moments, the screen begins to flicker, an NVIDIA notification appears, and the application becomes unresponsive before crashing.
My system specifications are:
Operating System: Windows 11 (fully updated)
GPU: NVIDIA GeForce RTX 4080 (using the latest drivers)
I have performed extensive troubleshooting based on the information in your documentation. The following steps have not resolved the issue:
I have installed the latest GPU drivers.
Running the app with --no-gpu fails to launch it at all.
I have uninstalled and reinstalled Warp completely.
I have confirmed that my antivirus and firewall are not blocking the application.
I have tried the documented workaround using the $env:WGPU_BACKEND="vulkan,gl" flag. This prevented the "not responding" error, but it caused the screen to flicker constantly, making the application unusable.
Upon reviewing the Windows Event Viewer logs, I have identified a critical detail. The warp.exe error (Application Hang) occurs at the exact same time as an Application Error for pwsh.exe (PowerShell). This suggests that the issue is not just in Warp's rendering, but in a specific conflict that arises when Warp attempts to render the PowerShell shell using my GPU's drivers.
This interaction appears to be the root cause of the crash. I have included the relevant log entries below for your review.
To reproduce
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Windows
Operating system and version
windows 11
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?
Yes, this issue prevents me from using Warp daily.
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