Thanks for working on this, the current result from getGPUFeatureStatus is limited and not really helpful for all cases. What would be better is to have an action in the help menu Help > Show GPU status and it should open a new window similar to process explorer that loads chrome://gpu url which will have all the necessary stats from the runtime.

Thanks for working on this, the current result from getGPUFeatureStatus is limited and not really helpful for all cases. What would be better is to have an action in the help menu Help > Show GPU status and it should open a new window similar to process explorer that loads chrome://gpu url which will have all the necessary stats from the runtime.

Oh, that makes sense. I will work on this.

@deepak1556 I got some updates in this PR.
Now it will open a new BrowserWindow to load the chrome://gpu URL with a Help > Show GPU status command.
I'm not sure if I should implement it in the browser environment since VSCode provides a Web edition.

• In edge we can open edge://gpu or chrome://gpu which will redirect to edge://gpu automatically.
• In firefox we can open about:support.
• But I'm not finding a similar page in safari.
  
  
  
  

The feature is only needed in desktop, for web users can get the info from respective browsers using the standard way.

Sorry for the late review here but I wonder if the added files and services is a bit overkill for what we want to achieve here? I think a service is good if there are multiple users but I think here what we want is to open a window with the GPU info.

We could simply do that from the nativeHostMainService exposing a new method for it (such as the openDevtools method we already have) and put all the code there. In the end that would mean we just have 2 files to change?

Sorry I missed the ping on this. Changes LGTM but we have currently closed the main branch for release/1.94 preparation. I will merge this in once the branch is open again.

@deepak1556 Could we merge into the main branch? Just resolved a merge conflict.