profile
viewpoint

digeff/angular 0

One framework. Mobile & desktop.

digeff/nodejstools 0

Node.js Tools for Visual Studio

digeff/noice-json-rpc 0

Noice Json RPC exposes a clean ES6 Proxy and Promise based interface for JSON-RPC2 Clients and Servers

digeff/old-vscode-pwa 0

VSCode PWA Extension

digeff/react-native 0

A framework for building native apps with React.

digeff/vscode 0

Visual Studio Code

digeff/vscode-chrome-debug 0

Debug your JavaScript code running in Google Chrome from VS Code.

digeff/vscode-chrome-debug-core 0

A library for implementing VS Code debug adapters for targets that implement the Chrome Debugging Protocol.

digeff/vscode-debugadapter-node 0

Debug adapter protocol and implementation for VS Code.

digeff/vscode-node-debug 0

A VS Code debug adapter for node

issue closedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome-nightly
  • Extension Version: 2020.2.15300
  • OS Version: Windows_NT ia32 6.1.7601
  • VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory: :warning:c:\Users\usuario\AppData\Local\Temp\msjsdiag.debugger-for-chrome-nightly-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

closed time in 5 days

Viper-76

issue commentmicrosoft/vscode-chrome-debug

Extension causes high cpu load

We have a new debugger and this extension is no longer maintained (see readme)

Viper-76

comment created time in 5 days

issue openedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome-nightly
  • Extension Version: 2020.2.15300
  • OS Version: Windows_NT ia32 6.1.7601
  • VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory: :warning:c:\Users\usuario\AppData\Local\Temp\msjsdiag.debugger-for-chrome-nightly-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

created time in 5 days

issue closedmicrosoft/vscode-chrome-debug

Extension issue

  • Issue Type: Bug
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 10.0.19041
  • VSCode version: 1.51.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 12604,
		"activateCallTime": 1,
		"activateResolvedTime": 0,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "msjsdiag.debugger-for-chrome",
				"_lower": "msjsdiag.debugger-for-chrome"
			},
			"activationEvent": "onDebugResolve:chrome"
		}
	},
	"runtimeErrors": []
}

closed time in 6 days

codeNameM1

issue commentmicrosoft/vscode-chrome-debug

Extension issue

This extension is no longer maintained (see readme). Let us know if you have issues with the new debugger.

codeNameM1

comment created time in 6 days

issue openedmicrosoft/vscode-chrome-debug

Extension issue

  • Issue Type: Bug
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 10.0.19041
  • VSCode version: 1.51.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

created time in 6 days

issue closedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 10.0.19041
  • VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory: :warning:c:\Users\DELL\AppData\Local\Temp\msjsdiag.debugger-for-chrome-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

closed time in 11 days

Mlwatson1048

issue commentmicrosoft/vscode-chrome-debug

Extension causes high cpu load

This extension is no longer actively developed. We have a new debugger, which is the default unless you set debug.javascript.usePreview: false. We recommend updating your VS Code version and switching over to that; please file an issue if there's something that doesn't work right or othewise prevent you from switching.

Mlwatson1048

comment created time in 11 days

issue openedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 10.0.19041
  • VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory: :warning:c:\Users\DELL\AppData\Local\Temp\msjsdiag.debugger-for-chrome-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

created time in 11 days

issue commentmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

We're doing custom "native" processing, yeah, which in theory could be possible to open-source and reuse in VSCode, but I think using existing DWARF support in the VSCode C++ extension might be more straighforward and in line with users' expectations as it would allow to use same configs and workflow as for regular C++ code.

EKALEB

comment created time in 13 days

issue openedmicrosoft/vscode-edge-debug2

Extension issue

  • Issue Type: Bug
  • Extension Name: debugger-for-edge
  • Extension Version: 1.0.15
  • OS Version: Windows_NT x64 10.0.18363
  • VSCode version: 1.50.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

created time in 13 days

issue commentmicrosoft/vscode-edge-debug2

Launch with default profil

Use runtime arguments to choose preferred profile.

Instructions

  1. Launch your Edge browser
  2. Choose the profile you would like to use when debugging
  3. In the Address Bar type edge://version/
  4. Next to "Profile path" you will see the path to the current profile in use C:\Users\YourUserName\AppData\Local\Microsoft\Edge\User Data\Profile 1 example from Windows 10
  5. In your launch configuration (launch.json), add the following if your profile is named "Profile 1"
    {
      "configurations": [
        {
          // ...
          "runtimeArgs": ["--profile-directory='Profile 1'"]
        }
      ]
    }
    
    Don't forget single quotes if the profile name contains spaces. Also quotation or escaping can vary depending on the system, the above example is from a Windows 10 environment.

Final note, the profile name - above the avatar or profile picture - can differ from the profile folder name. For example, If you create a new user profile in Edge and name it My Dev Profile, the folder created under ...Edge\User Data\ could be given the name Profile 3, and this is the name you should use. So make sure you are using the correct name as instructed in the steps above.

MGMehdi

comment created time in 14 days

issue closedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 6.1.7601
  • VSCode version: 1.47.2

:warning: Make sure to attach this file from your home-directory: :warning:C:\Users\USER\msjsdiag.debugger-for-chrome-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

closed time in 15 days

MrJack404

issue commentmicrosoft/vscode-chrome-debug

Extension causes high cpu load

This extension is no longer actively developed. We have a new debugger, which is the default unless you set debug.javascript.usePreview: false. We recommend updating your VS Code version and switching over to that; please file an issue if there's something that doesn't work right or othewise prevent you from switching.

MrJack404

comment created time in 15 days

issue openedmicrosoft/vscode-chrome-debug

Extension causes high cpu load

  • Issue Type: Performance
  • Extension Name: debugger-for-chrome
  • Extension Version: 4.12.11
  • OS Version: Windows_NT x64 6.1.7601
  • VSCode version: 1.47.2

:warning: Make sure to attach this file from your home-directory: :warning:C:\Users\USER\msjsdiag.debugger-for-chrome-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

created time in 15 days

issue commentmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

Thanks for the heads up!

The approach we've taken for this in similar scenarios--currently for React Native and Blazor--is to have the implementing language stand up a CDP-speaking proxy that we can connect to. This is not an entirely trivial amount of work, but neither is building a debugger. The main advantages to this are:

  • Both DevTools and would VS/VS Code's debugger (or WebStorm or any other CDP-speaking debugger) would work without any specific work on either end.
  • It's easy for the proxy to pass-through to the browser with arbitrary smartness and to debug across the wasm world and the DOM/JS world. Additional functionality we might add in the future (e.g. DOM inspector) can be passed through as well.

In DevTools, are you trying to understand DWARF 'natively' or are you some other tool to drive it?

EKALEB

comment created time in 16 days

issue commentmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

Note that Emscripten and DevTools has been since working on integration of DWARF for richer debugging experience instead of the source map approach; I don't know how it would be possible to implement similar support in VSCode, but perhaps there is a way to make VSCode Chrome Debug and the official C/C++ extension to talk to each other when Wasm is encountered?

EKALEB

comment created time in 16 days

issue openedmicrosoft/vscode-edge-debug2

Microsoft Edge Chromium will not attach to server running React app

  • VS Code Version: 1.51.0
  • Log file (set "trace": true in launch config): Checked 'C:\Users\cpayne\AppData\Local\Temp', but no log file was present (was looking for the file 'vscode-edge-debug2.txt'

Steps to reproduce:

  1. Disabled all installed debuggers in VS Code
  2. Enabled Debugger for Microsoft Edge, v1.0.15
  3. Closed and reloaded VS Code as administrator.
  4. Installed latest of 'react-app-polyfill', and ran 'npm run build' on my React app to ensure everything compiles.
  5. Deleted launch.json file
  6. Tried configuring Edge debugger by following the instructions here: https://docs.microsoft.com/en-us/microsoft-edge/visual-studio-code/debugger-for-edge
  7. I added the launch configuration, ran the 'start msedge' command, attached Edge to VS Code, then ran 'yarn start'.

Expected Behavior: Running 'yarn start' serves the React app and opens a tab/window in Microsoft Edge. Once the app is running, I can attach my debugger to the running application and debug.

Actual Behavior: VS Code serves the app, but launces a tab in Chrome. There is nothing in my launch.json file regarding launching or attaching a process to anything except MS Edge. If I try to navigate to the port where Edge is supposed to be listening (http://localhost:8080), I just get a 'ERR_CONNECTION_REFUSED' error message.

created time in 16 days

push eventmicrosoft/vscode-node-debug2

Connor Peet

commit sha a1d8b5495938a3525927f88d0b572b5ce541e5e5

Update issue templates

view details

push time in 16 days

push eventmicrosoft/vscode-chrome-debug

Connor Peet

commit sha aba968f7655d876f4f143d635c8b8183bf6f6b3d

Update bug_report.md

view details

push time in 16 days

issue closedmicrosoft/vscode-chrome-debug

Problem inside Angular Observables

version: 1.50.1 chrome: 83.0.4103 OS:Windows 10 my launch.json { "type": "chrome", "request": "attach", "name": "Attach to Chrome", "port": 9222, "webRoot": "${workspaceFolder}" }

Steps:

  1. add a break point inside an Observable of angular project
  2. when u hover over this inside an Observable it should show the current class variables and functions but instead it shows the observable scope subscribe
  3. when i try to check any variable it show undefined. undefined
  4. but the local variable declared inside the Observable are working fine.
  5. if i check the same variable inside chrome debug console chrome

closed time in 16 days

kvinay3

issue closedmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

I got the index.wasm, index.wasm.map and index.js generated from main.cpp, but I can't set breakpoints in main.cpp. I've checked the content of index.wasm.map, it seemed correct to me. I wonder if the debugger detected index.wasm.map from the wasm files. By the way, these files work fine in Chrome Explorers' devtools, and the the breackpoints in main.cpp works Uploading vscode-chrome-debug.txt…

  • VS Code Version: 1.42

closed time in 16 days

EKALEB

issue commentmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

Thanks for the tag. I admittedly haven't looked into wasm much/at all yet in js-debug didn't know sourcemaps worked for wasm files -- makes sense though, just bytes instead of characters. I'll move the referenced issue to js-debug and use it as the issue to track wasm support for js-debug. Assuming that we don't want to devote the time to add it to chrome-debug-core which is no longer in use by any active 1st party debugger.

EKALEB

comment created time in 16 days

issue commentmicrosoft/vscode-chrome-debug

The wasm files can't be debugged in vscode

@connor4312 does js-debug do what it needs to do here?

EKALEB

comment created time in 16 days

issue closedmicrosoft/vscode-chrome-debug

Move setExpression to -core

Tracking the continuing discussion for this API, added to chrome-debug in https://github.com/Microsoft/vscode-chrome-debug/pull/612

Added to DAP in https://github.com/Microsoft/vscode-debugadapter-node/issues/167

closed time in 16 days

roblourens

issue closedmicrosoft/vscode-chrome-debug

Ease consumption of debug adapter in other tools by publishing it on npmjs

This is related to #927 . Other IDEs that have support for the Debug Adapter Protocol can take advantage of the Chrome Debug Adapter implemented in this project. However, consuming this Debug Adapter currently requires some hacky steps (fetching extension, extracting subset, npm pack/install...). It would really be easier if the debugAdapter (the server module) would be published on npmjs as a standalone artifact.

closed time in 20 days

mickaelistria

issue commentmicrosoft/vscode-chrome-debug

Ease consumption of debug adapter in other tools by publishing it on npmjs

This debugger has been superceded and will not receive m/any more updates.

mickaelistria

comment created time in 20 days

issue closedmicrosoft/vscode-node-debug2

Publish as dedicate node module

This debug adapter can be reused by other IDEs and editors. To make it easier to consume, it would be great to have it published on npm.js as a dedicated module. Current workaround involves either building from source or extracting it from VSCode delivery.

closed time in 20 days

mickaelistria

issue commentmicrosoft/vscode-node-debug2

Publish as dedicate node module

This debugger has been superceded and is not expected to receive m/any more updates.

mickaelistria

comment created time in 20 days

more