Open planet-venkus opened 2 months ago
Hi @planet-venkus, could you include the output of your Warp logs so we can debug further?
@alokedesai These are the logs from the exact moment the monitor froze (2024-06-27T15:47:xx). One of my referrals also reported the same problem when using a lenovo monitor.
2024-06-27T15:45:53Z [INFO] Flushed telemetry events. 2024-06-27T15:46:23Z [INFO] Checking for update on channel stable_release. Update id is mLnx7Qu 2024-06-27T15:46:23Z [INFO] Fetching channel versions (without changelogs) from Warp server 2024-06-27T15:46:23Z [INFO] regenerating access token 2024-06-27T15:46:23Z [INFO] Start to flush telemetry events to Segment 2024-06-27T15:46:23Z [INFO] Dropping empty telemetry batch 2024-06-27T15:46:23Z [INFO] Flushed telemetry events. 2024-06-27T15:46:23Z [INFO] Received channel versions from Warp server: dev: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.27.08.02.dev_00", update_by: None, soft_cutoff: Some("v0.2023.05.12.08.03.dev_00") }, overrides: [] }; preview: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.27.08.02.preview_00", update_by: None, soft_cutoff: None }, overrides: [] }; canary: ChannelVersion { version_info: VersionInfo { version: "v0.2022.09.29.08.08.canary_00", update_by: None, soft_cutoff: None }, overrides: [] }; beta: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.25.08.02.beta_00", update_by: None, soft_cutoff: None }, overrides: [] }; stable: ChannelVersion { version_info: VersionInfo { version: "v0.2024.06.18.08.02.stable_03", update_by: None, soft_cutoff: Some("v0.2024.05.07.08.02.stable_02") }, overrides: [VersionOverride { predicate: TargetOS(Linux), version_info: VersionInfo { version: "v0.2024.06.18.08.02.stable_04", update_by: None, soft_cutoff: None } }] } 2024-06-27T15:46:23Z [INFO] No update available 2024-06-27T15:46:53Z [INFO] Start to flush telemetry events to Segment 2024-06-27T15:46:53Z [INFO] Dropping empty telemetry batch 2024-06-27T15:46:53Z [INFO] Flushed telemetry events. 2024-06-27T15:47:09Z [INFO] window resized 2024-06-27T15:47:09Z [INFO] dispatching global action for workspace:save_app 2024-06-27T15:47:09Z [INFO] window resized 2024-06-27T15:47:09Z [INFO] dispatching global action for workspace:save_app 2024-06-27T15:47:09Z [WARN] redraw_frame was called 3 times before the frame was drawn 2024-06-27T15:47:23Z [INFO] Start to flush telemetry events to Segment 2024-06-27T15:47:23Z [INFO] Dropping empty telemetry batch 2024-06-27T15:47:23Z [INFO] Flushed telemetry events. 2024-06-27T15:47:39Z [INFO] active window changed: Some(WindowId(0)) 2024-06-27T15:47:39Z [INFO] dispatching global action for root_view:update_quake_mode_state 2024-06-27T15:47:39Z [INFO] dispatching global action for workspace:save_app 2024-06-27T15:47:40Z [INFO] active window changed: None 2024-06-27T15:47:40Z [INFO] dispatching global action for root_view:update_quake_mode_state 2024-06-27T15:47:40Z [INFO] dispatching global action for workspace:save_app 2024-06-27T15:47:53Z [INFO] Start to flush telemetry events to Segment 2024-06-27T15:47:53Z [INFO] Dropping empty telemetry batch 2024-06-27T15:47:53Z [INFO] Flushed telemetry events.
Same issue here!
@alokedesai @aesbetancourt did you find a solution?? i feel warp is not strong enough for programmers if this bug persists.
Hi @planet-venkus, if you enable use of your integrated GPU does this "fix" the issue?
You can do that in Settings > Features > Performance > Prefer rendering new windows with integrated GPU(low power).
Also, could you send your full warp logs so we can debug further?
Hi @planet-venkus Following up here, are you still experiencing this issue?
Hello @alokedesai. Sorry for my late response as i was waiting for the issue to reoccur. Turning ON "Prefer rendering new windows with integrated GPU(low power)" has resolved the issue.
Dupe Check
Describe the bug
This bug occurs when the warp terminal is running on additional screen. The second monitor screen freezes and unless i remove and reconnect the monitor, the second screen is frozen. This bug occurred on all the monitors i connected my laptop to.
Monitors tested: Dell, Benq Laptop: Razor Blade 15
To reproduce
Its stochastic and needs more analysis when the bug occurs. WIll definitely occur when using second monitor with laptop.
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
22.04
Shell Version
No response
Current Warp version
v0.2024.06.18.08.02.stable_04
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 a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None