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

Internal error: illegal access for variables and watch expressions #6867

Closed
isidorn opened this issue May 25, 2016 · 4 comments
Closed

Internal error: illegal access for variables and watch expressions #6867

isidorn opened this issue May 25, 2016 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded

Comments

@isidorn
Copy link
Contributor

isidorn commented May 25, 2016

  • VSCode Version: alpha
  • OS Version: os x
  • node version: had node 6.2 installed but reverted back to 6.1 and still see this behavior

Steps to Reproduce:

  1. Debug any simple js application
  2. Try to evaluate console in watch or repl -> get an 'Internal error: illegal access'
  3. I also get this error for some variables in the variables view

screen shot 2016-05-25 at 12 53 14

@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels May 25, 2016
@weinand weinand added this to the May 2016 milestone May 25, 2016
@weinand weinand added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label May 26, 2016
@weinand weinand modified the milestones: Backlog, May 2016 May 26, 2016
@rostacik
Copy link

rostacik commented May 30, 2016

Hi gents.
Same error here. Windows 8.1, VS Code 1.1.1 + insiders also.
vscode

@weinand
Copy link
Contributor

weinand commented May 30, 2016

@rostacik that's a V8 bug in node 6.x. Our workaround for this problem seems to work for most, but not for all. Until node 6.2.1 arrives the workaround for those that are hit by this is to use node 5.x.

@rostacik
Copy link

@weinand yes sir, I can confirm that with v4.4.5 VS Code behaves as expected, thanks for quick reply.

@weinand
Copy link
Contributor

weinand commented Jun 3, 2016

This problem no longer occurs in node v6.2.1.

@weinand weinand closed this as completed Jun 3, 2016
@weinand weinand removed this from the Backlog milestone Jun 3, 2016
@weinand weinand assigned isidorn and unassigned weinand Jun 3, 2016
@isidorn isidorn added the verified Verification succeeded label Jun 16, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
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 debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants