You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed when extending the global variable with jsdom().parentWindow, and also including a large library such as bluebird or engine.io, JSDOM errors with a maximum call stack size exceeded.
JSDOM does continue to function if wrapped in a try...catch statement, so would it be possible to gracefully handle this error within JSDOM?
_(global).extend(jsdom().parentWindow)
var engine = require('engine.io')
Results in:
node_modules/jsdom/lib/jsdom/browser/index.js:121
this.setTimeout = function (fn, ms) { return startTimer(setTimeout, clearT
^
RangeError: Maximum call stack size exceeded
I understand the use case is quite bizarre, but I'm curious as to what this error really means.
The text was updated successfully, but these errors were encountered:
It's been a while since I've worked on JSDOM, but IIRC the JSDOM timer implementation keeps track of open timers so we can cancel them in window.close to avoid memory leaks from dangling timers.
I've noticed when extending the global variable with
jsdom().parentWindow
, and also including a large library such asbluebird
orengine.io
, JSDOM errors with a maximum call stack size exceeded.JSDOM does continue to function if wrapped in a
try...catch
statement, so would it be possible to gracefully handle this error within JSDOM?Results in:
I understand the use case is quite bizarre, but I'm curious as to what this error really means.
The text was updated successfully, but these errors were encountered: