Running all examples periodically hangs on Windows for Node v5

[kgryte]

Checklist

Please ensure the following tasks are completed before filing an issue.

• Read and understood the Code of Conduct.
• Searched for existing issues and pull requests.
• If this is a general question, searched the FAQ for an existing answer.
• If this is a feature request, the issue name begins with RFC: .

Description

Description of the issue.

Running make examples on Node.js v5 on Windows periodically stalls. Possibly due to a long running example.

Note: unable to personally reproduce as do not have access to a Windows machine. Came across the bug due to periodically failing builds on AppVeyor.

Related Issues

Does this issue have any related issues?

No.

Questions

Any questions for reviewers?

No.

Other

Any other information relevant to this issue (or feature request)? This may include screenshots, references, stack traces, sample output, and/or implementation notes.

AppVeyor builds periodically fail due to this bug. Bug always occurs on Node v5. Collaborator was able to reproduce the issue on local Windows machine.

Reproduction

If this issue is a bug report, what steps are required to reproduce the unexpected output? (If this is a feature request, remove this section.)

In order to reproduce this bug, do the equivalent of the following on Windows:

$ nvm use 5
$ make examples

Expected Results

What are the expected results? (If this is a feature request, remove this section.)

Examples should successfully run and finish.

Actual Results

What are the actual results? (If this is a feature request, remove this section.)

Command hangs.

Environments

If this issue is a bug report, what environments are affected; e.g., Node v0.4.x, Chrome, IE 11? If Node.js, include the npm version, operating system, and any other potentially relevant platform information. (If this is a feature request, remove this section.)

The following environments are affected:

• Windows, Node.js v5

[kgryte]

We no longer us AppVeyor and Node.js v5 is an older, unstable Node.js version, so probably not worth investigating.