Extension goes "blank" / Grey Screen

[wolverin0]

Type: Bug

using roo or cline in multiple vsc windows crashes the window leaving a "gray empty page" and you have to reload the whole vsc for it to come back

Extension version: 3.11.3
VS Code version: Code 1.97.2 (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-14900K (32 x 3187)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.77GB (34.98GB free)
Process Argv	--crash-reporter-id c2163186-385c-4e5a-8b05-9c491fb4bb42
Screen Reader	no
VM	0%

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
f27dg485:31264363
f5992895:31277799
jda6j935:31233686
pythoneinst12cf:31262606
bgtreat:31268568
fh1c7952:31258891
4gafe986:31271826
31787653:31262186
3e8i5726:31271747
0339e702:31259951
49da9784:31264548

[ianlintner]

I was running 4 instances of cursor and all of them gray screen of death at the same time mac. I deal with it half a dozen times during the day.

[victortong-git]

I tried VS Code, VS Code Insider on Windows and Linux. All these platforms and VS Codes face same issue.

[hannesrudolph]

1. Starting conditions (software state, settings, environment)
2. Precise actions taken (every click, selection, input)
3. Clearly observe and report outcomes

[appscaptain]

Observe exactly the same on MacOS in VSC.
I am just in the middle of a chat with DeepSeek R1 or Gemini 2.5 Pro Exp etc.. Last time:

Up at a context window of around 57k of the 64k in DeepSeek R1. It needs to run a terminal command. I approve. It says API Request... it is Thinking for a while and the whole interface becomes blank (as shown in the screenshot) during the thinking. I have to quit and relaunch the app. And from this time it keeps getting blank when I try to run the terminal command.

If I wait and let it execute I see nothing on the screen so I jsut let it sit for a while. Then I quit and restart and reopen the chat and I see it has completed the command and is waiting run the next command with a Resume Task / Cancel buttons.

I resume task - it starts typing the command in the next Run Command field and it just becomes grey during that.

[KJ7LNW]

Unfortunately we do not have a reliable way to reproduce it and there are no logs indicating the problem. Next time it happens immediately try this:

• help -> toggle development tools -> console -> show all levels (so that it does not filter anything)

Are there any obvious back traces that could be helpful for pinning down the issue?

From there I know that this "fixes" it, but it triggers a reload of active extension state:

• ctrl+shift+p -> reload window

If anyone has a reliable way to trigger the issue then we may be able to investigate further.

[Xytronix]

#2547 , #2489 , #2391 duplicate, attached you find the log.

this happens every 30-60 minutes for me using both API and Copilot API. Issue involves apply_diff.

macOS 15.4

vscode-app-1744709690872.log

vscode-app-1744717520785.log

[KJ7LNW]

Issue involves apply_diff

it appears to involve apply_diff but only because it shows a split window in vscode:

inlineDiffDeletedCodeMargin.ts:108 [Violation] 'requestIdleCallback' handler took 104ms

I think this is the relevant section of the log:

extensionsProposedApi.ts:131 [Violation] 'message' handler took 155ms
index.html?id=fc07d5d9-f264-47e9-816c-9683ed7fe8f0&origin=03a90aa0-ae8f-4c57-aa2d-5b5057dc32b0&swVersion=4&extensionId=eamodio.gitlens&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&purpose=webviewView:1060 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
(anonymous) @ index.html?id=fc07d5d9-f264-47e9-816c-9683ed7fe8f0&origin=03a90aa0-ae8f-4c57-aa2d-5b5057dc32b0&swVersion=4&extensionId=eamodio.gitlens&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app&purpose=webviewView:1060
index.html?id=c401b4a3-126d-4bce-a57c-023569a5d2a4&origin=0fedabca-6735-411c-877e-0141ed52564f&swVersion=4&extensionId=eamodio.gitlens&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app:281 Found unexpected service worker controller. Found: vscode-webview://08lqflk26n8e027kmmlhlfmd7i1a5qs3g3qrtv3p7uv5ime1msf7/service-worker.js?v=4&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&id=95d08803-3a98-4108-9775-31f9caae3254&remoteAuthority=. Expected: service-worker.js?v=4&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&id=c401b4a3-126d-4bce-a57c-023569a5d2a4&remoteAuthority=. Waiting for controllerchange.
graph.js:2196 [Violation] 'requestAnimationFrame' handler took 247ms
[Violation] Forced reflow while executing JavaScript took 250ms
index.html?id=c401b4a3-126d-4bce-a57c-023569a5d2a4&origin=0fedabca-6735-411c-877e-0141ed52564f&swVersion=4&extensionId=eamodio.gitlens&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app:1060 [Violation] Avoid using document.write(). https://developers.google.com/web/updates/2016/08/removing-document-write
(anonymous) @ index.html?id=c401b4a3-126d-4bce-a57c-023569a5d2a4&origin=0fedabca-6735-411c-877e-0141ed52564f&swVersion=4&extensionId=eamodio.gitlens&platform=electron&vscode-resource-base-authority=vscode-resource.vscode-cdn.net&parentOrigin=vscode-file%3A%2F%2Fvscode-app:1060
inlineDiffDeletedCodeMargin.ts:108 [Violation] 'requestIdleCallback' handler took 104ms
inlineDiffDeletedCodeMargin.ts:108 [Violation] 'requestIdleCallback' handler took 105ms
graph.js:1 [Violation] 'setInterval' handler took 54ms
[Violation] Forced reflow while executing JavaScript took 30ms
graph.js:1 [Violation] 'setInterval' handler took 60ms
inlineDiffDeletedCodeMargin.ts:108 [Violation] 'requestIdleCallback' handler took 379ms

unfortunately that is not our code:

https://github.com/microsoft/vscode/blob/main/src/vs/editor/browser/widget/diffEditor/components/diffEditorViewZones/inlineDiffDeletedCodeMargin.ts

but I think it does highlight that something is happening with the vs code split window that is slow, and we are invoking that... so the question is this: is there is something we can do more that is more efficient in terms of displaying the split-edit window during diff application ?

alternatively is there a workaround so we can crank up [Violation] 'requestIdleCallback' handler took 104ms limits?