You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
isidorn opened this issue
May 25, 2016
· 4 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
node version: had node 6.2 installed but reverted back to 6.1 and still see this behavior
Steps to Reproduce:
Debug any simple js application
Try to evaluate console in watch or repl -> get an 'Internal error: illegal access'
I also get this error for some variables in the variables view
The text was updated successfully, but these errors were encountered:
isidorn
added
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
labels
May 25, 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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeeded
Steps to Reproduce:
console
in watch or repl -> get an 'Internal error: illegal access'The text was updated successfully, but these errors were encountered: