-
Notifications
You must be signed in to change notification settings - Fork 408
Node Process crashes with 'Call stack exceeded' error in zone-node on Node 10 #1164
Comments
Please provide a reproduce repo, thanks! |
@JiaLiPassion I'm having trouble isolating what part of the code is triggering the issue. My instinct was that it had something to do with the Domain API in Node, but a small HTTP server that uses domains and Zone doesn't seem to trigger a repro of this case. It seems to have something to do with calling prependListener as from the stack trace you can see the infinite loop that occurs and causes the stack to overflow. I'll keep trying to see if I can call these methods to get this to happen. |
I'm seeing the same issue after upgrading from Node 8 to 10.14.1. Downgrading resolves it. Sadly I don't have a simple way to reproduce it as this isn't a direct dependency of mine, so I'm not sure how zone.js is being used by my dependency. |
It looks like my dependency is specifying 0.8.20. Sorry I can't share it, it's internal to my company. 🙁 |
I still need to look further into how my dependency uses zone.js, but I'm actually seeing the error when running my unit tests. Specifically, this line from Mocha:
In a Node console I could reproduce this more directly with:
Still need to look into how we're using zone.js, but thought this might be helpful. |
Thanks, @nbryan, is that possible to share your |
@JiaLiPassion Actually the reproduction gets even simpler: require('zone.js');
process.on('uncaughtException', function() {
console.log('wat');
}); If I run that in the Node REPL I get an error. If I save it to a a file and run it with |
@nbryan, @justinappler, thanks! I have fixed this one #1170 |
… endless loop update yarn
@JiaLiPassion Wow, thanks for the quick responses and turnaround on a fix! |
zone.js version: 0.8.26
Node Version: 10.13.0
When running my Angular Universal application in Node 10.13, using
zone.js/dist/zone-node
version 0.8.26, the process crashes at startup with the following Stack Trace:The error does not reproduce when I downgrade to Node 8 (8.9.4).
The text was updated successfully, but these errors were encountered: