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

Issue reporter takes 7 seconds to render in Windows in latest Insiders #48617

Closed
ramya-rao-a opened this issue Apr 24, 2018 · 1 comment
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug issue-reporter Issue reporter widget issues verified Verification succeeded
Milestone

Comments

@ramya-rao-a
Copy link
Contributor

Issue Type: Bug

  • Open the issue reporter
  • The window opens quickly but is blank
  • Takes about 7 seconds to render anything in the Window

Happens only in the Insiders
Stable is fine

VS Code version: Code - Insiders 1.23.0-insider (b845ce9, 2018-04-24T05:17:07.677Z)
OS version: Windows_NT x64 10.0.15063

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz (8 x 3492)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 31.92GB (18.10GB free)
Process Argv C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe
Screen Reader no
VM 0%
Extensions: none
@vscodebot vscodebot bot added the insiders label Apr 24, 2018
@ramya-rao-a ramya-rao-a added the issue-reporter Issue reporter widget issues label Apr 24, 2018
@ramya-rao-a ramya-rao-a added this to the April 2018 milestone Apr 24, 2018
@RMacfarlane
Copy link
Contributor

With ebf9c8c, I updated the windows-process-tree package which now does the cpu usage calculation in a worker thread. The render time for the issue reporter is lower, more like 3 seconds, but still not as good as stable. Previously a separate process was spawned to list processes, so I think the time could still be improved by forking from main

@RMacfarlane RMacfarlane added the bug Issue identified by VS Code Team member as probable bug label Apr 26, 2018
@tsalinger tsalinger added the verified Verification succeeded label Apr 27, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug issue-reporter Issue reporter widget issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants