-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
Windows 10 access violation with debugger #5268
Labels
windows
Issues and PRs related to the Windows platform.
Comments
Trott
added a commit
to Trott/io.js
that referenced
this issue
Feb 17, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: nodejs#5268 Fixes: nodejs#4343
Trott
added a commit
to Trott/io.js
that referenced
this issue
Feb 19, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: nodejs#5268 Fixes: nodejs#4343 PR-URL: nodejs#5269 Reviewed-By: James M Snell <jasnell@gmail.com>
rvagg
pushed a commit
that referenced
this issue
Feb 21, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: #5268 Fixes: #4343 PR-URL: #5269 Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins
pushed a commit
that referenced
this issue
Mar 1, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: #5268 Fixes: #4343 PR-URL: #5269 Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins
pushed a commit
that referenced
this issue
Mar 1, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: #5268 Fixes: #4343 PR-URL: #5269 Reviewed-By: James M Snell <jasnell@gmail.com>
MylesBorins
pushed a commit
that referenced
this issue
Mar 2, 2016
Change test so that it passes on the occasional win10 access violation. The workaround here can be undone when issue 5268 is resolved. The test still detects the defect it was written to detect. There are two assertions that detect the defect and only one was disabled. Ref: #5268 Fixes: #4343 PR-URL: #5269 Reviewed-By: James M Snell <jasnell@gmail.com>
Debugger is being removed in the foreseeable future. This is unlikely to be fixed. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The environment:
Windows 10 (specifically run via the Node.js project Jenkins server)
The code:
Put this in a file in
test/parallel
:The issue:
The code usually runs OK but every once in a while, there's an access violation:
Here's a stress test showing the issue: https://ci.nodejs.org/job/node-stress-single-test/494/nodes=win10/console
Ref: #4343
The text was updated successfully, but these errors were encountered: