Skip to content
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

The background of main interface became grey. #155242

Open
tengyuntian opened this issue Jul 14, 2022 · 43 comments
Open

The background of main interface became grey. #155242

tengyuntian opened this issue Jul 14, 2022 · 43 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues notebook-output
Milestone

Comments

@tengyuntian
Copy link

Issue Type: Bug

I am using Jupyter Notebook in VS code. When I wheeled down the interface, it became grey. It happened before. Cannot see any pics clearly.

VS Code version: Code 1.69.1 (b06ae3b, 2022-07-12T08:21:24.514Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.80GB (21.36GB free)
Process Argv --crash-reporter-id 1c7786f7-3567-42d0-bd46-6060e36fc1d0
Screen Reader no
VM 0%
Extensions (7)
Extension Author (truncated) Version
copilot Git 1.31.6194
python ms- 2022.10.0
vscode-pylance ms- 2022.7.30
jupyter ms- 2022.6.1101950301
jupyter-keymap ms- 1.0.0
jupyter-renderers ms- 1.0.8
cpptools ms- 1.10.8

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdf:30486550

@rebornix
Copy link
Member

@tengyuntian can you please share a screenshot of what you were seeing?

@rebornix rebornix added the info-needed Issue requires more information from poster label Jul 15, 2022
@rebornix rebornix added this to the July 2022 milestone Jul 15, 2022
@tengyuntian
Copy link
Author

image
image

This happens again. The screenshot is attached.

@tjex
Copy link

tjex commented Jul 21, 2022

similar to my issue, but not identical behavior: #155820

@tengyuntian
Copy link
Author

tengyuntian commented Jul 22, 2022

Happened again. As the pic shows. I have to restart the .ipynb script.

image

@rebornix
Copy link
Member

@tengyuntian does it happen all the time or it only happens when you run some cells which emit rich outputs (with widgets)?

@rebornix rebornix modified the milestones: July 2022, August 2022 Jul 27, 2022
@tengyuntian
Copy link
Author

@tengyuntian does it happen all the time or it only happens when you run some cells which emit rich outputs (with widgets)?

It happened when I run cells with huge outputs. Also, it will happen sometimes when my ipynb is too long.

@rebornix rebornix added freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues notebook-output labels Aug 3, 2022
@rebornix
Copy link
Member

rebornix commented Aug 3, 2022

@tengyuntian thanks, that's really helpful. Would it make sense to provide a code snippet that get your VS Code into this state and share with us?

@tengyuntian
Copy link
Author

@tengyuntian thanks, that's really helpful. Would it make sense to provide a code snippet that get your VS Code into this state and share with us?

My script is growing longer, and the data need to be processed is becoming larger and larger with my research going on. So the "grey background" problems happen more and more often. I have to close the Jupyter Notebook and open it again to eliminate it. But this action results in longer waiting time for re-running all functions and importing all data. I think the key problem is that the amount of data is too large. The data is in .txt format. I have over 30 txt files with a total number of lines over 1 million. And they will be plotted into hundreds of plots to show the experimental results.

@rebornix rebornix removed the info-needed Issue requires more information from poster label Aug 4, 2022
@tengyuntian
Copy link
Author

I found that every time it is running hard and has no responding, if I scroll the interface up/down, it will crash and the background becomes grey, and all the outputs are hidden in the grey.

@tengyuntian
Copy link
Author

Capture

@tengyuntian
Copy link
Author

Is there anything I can do to avoid this? Every time I open a notebook with heavy data outputs, it will become grey and sometimes not responding. When it becomes grey, I cannot see or select any output and I have to re-open and re-run everything, then it happens again.

@rebornix rebornix modified the milestones: August 2022, September 2022 Aug 19, 2022
@kevindany
Copy link

I am running into the same issue these days again and again, is there any workaround to figure it out? I cannot do anything if I work with the visual studio code, help

@kelleyjbrady
Copy link

I am also experiencing this issue. VSCode+Jupyter is completely unusable.

@kelleyjbrady
Copy link

kelleyjbrady commented Sep 21, 2022

@kevindany, @tengyuntian I was able to resolve this by exporting my .ipynb to a .py file, then converting the .py file back into a .ipynb.

  1. Open the problem .ipynb
  2. CTRL+SHIFT+P
  3. Select Jupyter: Convert to Python Script
  4. Open the .py file
  5. Right click whitespace in the file and select Export Current File as Jupyter Notebook

Bonus points, you should be able to use git mv to carry over the versioning from the problematic file to the reconstituted one. (Rename the broken file to literally anything, then rename the reconstituted file to be same as the broken file's original name using git mv)

@kevindany
Copy link

@kevindany, @tengyuntian I was able to resolve this by exporting my .ipynb to a .py file, then converting the .py file back into a .ipynb.

  1. Open the problem .ipynb
  2. CTRL+SHIFT+P
  3. Select Jupyter: Convert to Python Script
  4. Open the .py file
  5. Right click whitespace in the file and select Export Current File as Jupyter Notebook

Bonus points, you should be able to use git mv to carry over the versioning from the problematic file to the reconstituted one. (Rename the broken file to literally anything, then rename the reconstituted file to be same as the broken file's original name using git mv)

It does not work :-(, it grays again

@rebornix rebornix removed this from the September 2022 milestone Sep 29, 2022
@rebornix rebornix added this to the August 2023 milestone Jul 24, 2023
@sdspieg
Copy link

sdspieg commented Aug 23, 2023

Same problem here. Also with a longish ipynb file. Surely there MUST be a way to solve this?

@gl2324
Copy link

gl2324 commented Aug 29, 2023

I also have the same problem. When I create plotly Figures that contain a lot of data vscode crashes in the behaviour described in the previous comments. Hopefully there is a solution soon

@rebornix rebornix modified the milestones: August 2023, September 2023 Aug 30, 2023
@arebs23
Copy link

arebs23 commented Sep 9, 2023

i also have a similar problem

@rebornix rebornix modified the milestones: September 2023, October 2023 Sep 26, 2023
@alec42
Copy link

alec42 commented Sep 28, 2023

me too

@rednag
Copy link

rednag commented Oct 2, 2023

I have the same issue. When I run my code in Jupyter Notebook I'm getting the following error -> how can I solve the problem for VSCode?

image

@wuzhonglijz
Copy link

Same problem here. Only installed python and jupyter plugins.

@misterspeedy
Copy link

Same problem here. Triggering code is below. Below about 20,000 data points it's fine. Above that it'll eventually "grey screen".

  • Plotly.NET, 4.2.0
  • Plotly.NET.Interactive, 4.2.1
open Plotly.NET
open Plotly.NET.TraceObjects
open Plotly.NET.LayoutObjects

let mapCentre = 
    exceedances
    |> Seq.averageBy (fun m -> m.Position.Longitude),
    exceedances
    |> Seq.averageBy (fun m -> m.Position.Latitude)

clusters
|> Seq.map (fun cluster -> 
    let coordsAsTuples =
        cluster.Exceedances
        // Mapbox assumes a Lon, Lat convention:
        |> Seq.map (fun ex -> ex.Position.Longitude, ex.Position.Latitude)
    Chart.PointMapbox(coordsAsTuples, Name=cluster.Id))
|> Chart.combine
|> Chart.withSize(1200, 800)
|> Chart.withMarkerStyle(Size=10)
|> Chart.withMarginSize(Left=0,Right=0,Top=30,Bottom=0)
|> Chart.withTitle("Clusters")
|> Chart.withMapbox(Mapbox.init(Style=StyleParam.MapboxStyle.OpenStreetMap, Center=mapCentre, Zoom=12.))

@rebornix rebornix modified the milestones: October 2023, November 2023 Oct 24, 2023
@MariamMahmoud11
Copy link

MariamMahmoud11 commented Nov 14, 2023

In my case : i was using pd.read_csv(file,low_memory=False) and when i removed the low_memory and restarted and cleared all outputs the grey boxes dissapeared

@rebornix rebornix modified the milestones: November 2023, December 2023 Nov 28, 2023
@rebornix rebornix modified the milestones: December / January 2024, February 2024 Jan 23, 2024
@rebornix rebornix modified the milestones: February 2024, March 2024 Feb 21, 2024
@rebornix rebornix modified the milestones: March 2024, April 2024 Mar 26, 2024
@obrooks-quest
Copy link

obrooks-quest commented Mar 27, 2024

Does everyone having this issue have the copilot extension?

Anecdotal, but his wasn't happening for me until I installed it. My only workaround has been to create a new notebook.

@aatj887
Copy link

aatj887 commented Apr 15, 2024

I do not have it and still happens to me.

@rebornix rebornix modified the milestones: April 2024, May 2024 Apr 23, 2024
@rebornix rebornix modified the milestones: May 2024, June 2024 May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues notebook-output
Projects
None yet
Development

No branches or pull requests