-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Extension goes "blank" #2270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I tried VS Code, VS Code Insider on Windows and Linux. All these platforms and VS Codes face same issue. |
|
Observe exactly the same on MacOS in VSC. 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. |
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:
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:
If anyone has a reliable way to trigger the issue then we may be able to investigate further. |
it appears to involve apply_diff but only because it shows a split window in vscode:
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 unfortunately that is not our code: 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 |
@PointerSoftware could you tell me what you were doing at the time that led upto this? Anything that could help us figure out why this is happening. |
Developer tools console does show some Roo issues:
|
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
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
A/B Experiments
The text was updated successfully, but these errors were encountered: