Tools: Running v1.14.11 never completes

[jeffposnick]

I'm seeing this behavior on OS X 10.11.4 and Node v5.9.1.

When using the CLI v1.14.8 (the previous version published to npm), everything worked as expected. Using the just-released v1.14.11, the vulcanize command run against the same source HTML never completes, and as per the top command, node ends up pegging one my CPUs at 100% indefinitely.

I'm unfortunately not sure what vulcanize is doing, but if there's any specific debugging steps you'd like me to take, I'd be happy to do that. The source HTML that I'm vulcanizing is part of a private project, but I can pass that along out of band if you're not able to reproduce.

[arturparkhisenko]

Win10 (Node v5.10.1 x64) v1.14.8 vs v1.14.11 on (i7-4790K) :smiling_imp::

@azakus @garlicnation ping! :8ball:

[kwaclaw]

Same here, on Windows, CPU at 100%. Maybe infinite loop:?

[jonnenauha]

Same in our build server, 100% on one CPU. Never completes. I use grunt-vulcanize =1.0.0 which seems to pull in the latest 1.14 in.

Ubuntu 14.04.4 LTS, Linux 3.19.0-30-generic x86_64

Edit: my local dev machine win 8.1 64bit works fine. Both systems have node 4.2.2.

[jonnenauha]

Looks like https://github.com/Polymer/grunt-vulcanize/blob/v1.0.0/package.json wants "vulcanize": "^1.9.3".

Not that familiar with the ^ notation in node. I assume it can upgrade to whatever minor version then like 1.14? Always thought that would mean that the patch can only be upgraded.

[xwsxethan]

+1 Same issue on ubuntu and running on Travis CI as part of our CI process.

[jeffposnick]

If folks are using gulp-vulcanize and don't have direct control over which version of vulcanize gets pulled in, you can create an npm-shrinkwrap.json file to force v1.14.8, which still works. (Hat tip to http://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions)

{
  "dependencies": {
    "gulp-vulcanize": {
      "version": "6.1.0",
      "dependencies": {
        "vulcanize": {
          "version": "1.14.8"
        }
      }
    }
  }
}

I'm sure a similar approach would work with grunt-vulcanize or the other wrappers.

[dfreedm]

Thanks for the reports. I think there may be an unexpected quadratic operation now. I'll take a look!