Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS #436

GordonSmith · 2016-05-27T04:19:31Z

Steps to reproduce

(install nodejs)
mkdir ./someDir
cd ./someDir
git clone https://github.com/hpcc-systems/Visualization.git
cd Visualization
git checkout candidate-1.14.x
npm install -g gulp
npm install -g bower
npm install
bower install
sudo apt-get install phantomjs
gulp unitTest

The text was updated successfully, but these errors were encountered:

benhillis · 2016-05-27T14:38:43Z

Thanks for the super clear repro steps! I tried this just now, is there a particular version of NodeJs I need? I'm going to first try with 6.2.0 and first I got this error in gulpfile.js:

SyntaxError: Identifier 'libs' has already been declared

I saw there were duplicate definitions of libs and bundles, so I removed one of the lines and now I hit a different error:

Error: Cannot find module 'jshint/src/cli'

Am I missing something?

GordonSmith · 2016-05-27T14:55:14Z

That was 4.x stable - clean install of bash etc.

FWIW I have been unable to reproduce it since (but haven't tried too hard). Since it was the very first thing I did in a clean bash environment I knew what steps I took.

Also it may have been on candidate-1.10.x or master when I actually ran it (but didn't think that that was the issue at the time...)

benhillis · 2016-05-27T14:56:49Z

I'll try it again with node v4.

@GordonSmith Could you check if you have a Memory.DMP file in c:\Windows?

GordonSmith · 2016-05-27T14:59:56Z

@benhillis I still have the Minidump if that is off interest?

benhillis · 2016-05-27T15:04:33Z

Yes very much so! Could you put it on a share somewhere and email a link to InsiderSupport@microsoft.com? If it's small enough you may just be able to attach it to the email. Include in the subject / message to forward to the WSL team. In the body of the email mention it is for benhill and russalex. Also kindly include the build number you're running.

GordonSmith · 2016-05-27T15:10:23Z

Done via attachment (512k).

benhillis · 2016-05-27T15:12:06Z

@GordonSmith Thank you very much, I'll let you know what I find out.

GordonSmith · 2016-06-08T20:34:18Z

Build 14361 - same blue screen - the one thing they both had in common is that they happened during the first boot into the updated OS.

Steps to reproduce:

(install nodejs 6.2.1)
mkdir ./someDir
cd ./someDir
git clone https://github.com/hpcc-systems/Visualization.git
cd Visualization
git checkout candidate-1.14.x
npm install -g gulp
npm install -g bower
npm install -g jshint
npm install
bower install
sudo apt-get install phantomjs
npm test

russalex · 2016-09-29T22:44:47Z

Ran through the steps above on the latest Insider build (14936) and did not get the blue screen. Not certain if it is the correct output, but no blue screen. Marking this one as fixed. Please let me know if this is not correct.

Output from my run was:

russ@DESKTOP-K1JHN54:~/tmp/Visualization$ node -v
v6.2.1
russ@DESKTOP-K1JHN54:~/tmp/Visualization$ npm test

> hpcc-viz@1.14.2-dev test /home/russ/tmp/Visualization
> gulp lint && gulp jscs && gulp unitTest && gulp build-all && gulp unitTestBuild && gulp unitTestBuildNonAMD

GordonSmith · 2016-09-30T04:03:14Z

I haven't seen a blue screen since and one of the patterns they had was that they only seemed to happen during the initial session after an update (or maybe that was because I backed off in some way). You can close fixed if you like.

The output above is only the first line of the entire lint, test, build, test cycle and I a have another issue open where PhantomJS appears to go into an infinite loop consuming memory: #489

GordonSmith · 2016-09-30T04:03:37Z

(closing will open if I can reproduce)

mnunezdm · 2019-02-27T09:49:06Z

I'm getting a blue screen when doing a npm install -g cells-cli npm version is 8.11.4 (Im trying to update npm to see if the error persists)

mikelid-zz · 2019-10-02T18:18:46Z

I have been getting multiple bsod on windows 10 / WSL / Ubuntu doing various relatively simple $npm install commands.
Incidentally why is npm so non-deterministic?? its behavior seems to indicate major race condition problems.

One log that I've collected a few times hence seems to be a culprit is:

2111 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
2112 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
2113 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
2113 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
2113 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux
2113 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
2114 verbose stack RangeError: Maximum call stack size exceeded
2114 verbose stack at RegExp.test ()
2114 verbose stack at isDepOptional (/usr/local/lib/node_modules/npm/lib/install/deps.js:423:45)

jfgrissom · 2019-11-09T16:43:51Z

I've been seeing the same behavior.

npm update causes a blue screen intermittently.

I've seen 6 blue screens this morning over a 4 hour time period.

I only have npm installed on WSL. I never installed npm on windows.

mnunezdm · 2019-11-18T10:46:59Z

I fix the blue screen issue deleting the windows npm installation and leaving only the wsl one, maybe erasing from the wsl path all the references to windows npm also do the trick

dorfsmay · 2020-01-22T23:54:55Z

I've been running into the same problem, blue screen + reboot on npm install and npm update, and uninstalling Windows' nodejs as suggested by @mnunezdm ~~has solved the issue (so far)~~ has reduced the frequency of crashed but not completely eliminated. I no longer use this setup.

ctsstc · 2020-04-24T11:19:11Z

I found out I had a directory with node & npm.

Had to run where.exe node & where.exe npm

Deleting them does not seem to have helped : (

I still get

npm ERR! Maximum call stack size exceeded

Sometimes I get BSODs other times it finishes installing just fine.

I'm on node v13.7.0
with 6.14.4

npm debug log

9813 verbose stack RangeError: Maximum call stack size exceeded
9813 verbose stack     at RegExp.test (<anonymous>)
9813 verbose stack     at isDepOptional (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:421:27)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:437:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9813 verbose stack     at failedDependency (/home/coder/.nvm/versions/node/v13.7.0/lib/node_modules/npm/lib/install/deps.js:453:9)
9814 verbose cwd /mnt/c/Users/Cody Swartz/Desktop/projects/others projects/hackbot
9815 verbose Linux 4.4.0-18362-Microsoft
9816 verbose argv "/home/coder/.nvm/versions/node/v13.7.0/bin/node" "/home/coder/.nvm/versions/node/v13.7.0/bin/npm" "i"
9817 verbose node v13.7.0
9818 verbose npm  v6.14.4
9819 error Maximum call stack size exceeded
9820 verbose exit [ 1, true ]

Maybe related to this, but didn't seem to help me
https://stackoverflow.com/questions/54835831/npm-err-maximum-call-stack-size-exceeded-when-npm-install-angular

Tried these with the same issue

node --stack-size=2000 $(which npm) install
node --stack-size=4000 $(which npm) install

I've tried multiple versions of nvm, and node all resulting in the same error

ctsstc · 2020-04-25T17:18:02Z

Was just trying to install a library today and got another bsod

Other times it's like certain npm operations don't go through unless you keep trying and then eventually do they do go through.

Part of me wonders if this is related to file IO concurrency. Maybe it's trying to install multiple things at a time while both want to finagle a similar dependency?

WSL has been great until recently on this project. I'm not sure what has changed. I've updated packages, npm, node, and it still seems to continue to happen no matter what versions I'm running.

ctsstc · 2020-04-25T17:21:59Z

I just found #4537 so I guess I'll post there as it's more recent and not closed

benhillis added the need-repro label May 27, 2016

GordonSmith changed the title ~~Blue Screen (Win 10 14352) Running PhantomJS~~ Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS Jun 8, 2016

russalex added fixed and removed need-repro labels Sep 29, 2016

GordonSmith closed this as completed Sep 30, 2016

samhocevar mentioned this issue Sep 7, 2020

Fix infinite recursion bug causing “Maximum call stack size exceeded” error npm/cli#1775

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS #436

Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS #436

GordonSmith commented May 27, 2016

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016 •

edited

Loading

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016 •

edited

Loading

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016

benhillis commented May 27, 2016

GordonSmith commented Jun 8, 2016

russalex commented Sep 29, 2016

GordonSmith commented Sep 30, 2016

GordonSmith commented Sep 30, 2016

mnunezdm commented Feb 27, 2019 •

edited

Loading

mikelid-zz commented Oct 2, 2019

jfgrissom commented Nov 9, 2019 •

edited

Loading

mnunezdm commented Nov 18, 2019

dorfsmay commented Jan 22, 2020 •

edited

Loading

ctsstc commented Apr 24, 2020 •

edited

Loading

ctsstc commented Apr 25, 2020

ctsstc commented Apr 25, 2020

Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS #436

Blue Screen (Win 10 14352 + 14361) Running npm / PhantomJS #436

Comments

GordonSmith commented May 27, 2016

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016 • edited Loading

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016 • edited Loading

benhillis commented May 27, 2016

GordonSmith commented May 27, 2016

benhillis commented May 27, 2016

GordonSmith commented Jun 8, 2016

russalex commented Sep 29, 2016

GordonSmith commented Sep 30, 2016

GordonSmith commented Sep 30, 2016

mnunezdm commented Feb 27, 2019 • edited Loading

mikelid-zz commented Oct 2, 2019

jfgrissom commented Nov 9, 2019 • edited Loading

mnunezdm commented Nov 18, 2019

dorfsmay commented Jan 22, 2020 • edited Loading

ctsstc commented Apr 24, 2020 • edited Loading

npm debug log

ctsstc commented Apr 25, 2020

ctsstc commented Apr 25, 2020

GordonSmith commented May 27, 2016 •

edited

Loading

GordonSmith commented May 27, 2016 •

edited

Loading

mnunezdm commented Feb 27, 2019 •

edited

Loading

jfgrissom commented Nov 9, 2019 •

edited

Loading

dorfsmay commented Jan 22, 2020 •

edited

Loading

ctsstc commented Apr 24, 2020 •

edited

Loading