22982 2013-08-16 04:40:33 +0000 Synchronous flag and stack consumption of DOM/Promises 2013-09-06 15:33:05 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED MOVED P2 normal --- 1 yhirano annevk mike mounir www-dom yusukesuzuki public-webapps-bugzilla oldest_to_newest 92136 0 yhirano 2013-08-16 04:40:33 +0000 fulfill, resolve and reject algorithms take the synchronous flag. If it is set the callbacks are processed synchronously i.e. simply called. If we chain promises and fulfill the original resolver, the promises will be resolved synchronously, which means stack frames in proportion to the length of the chain will be consumed. For example, the following statements leads to a stack overflow error in Chrome. var resolver; var id = 0; var N = 10000; var promise = new Promise(function(r) {resolver = r;}); for (var i = 0; i < N; ++i) { promise = promise.then(function() {console.log(id++)}); } resolver.resolve(4); Promise.every(Promise.every(...(Promise.every(promise))...)) has the same problem. 93114 1 annevk 2013-09-06 15:33:05 +0000 This is solved by the replacement hosted here: https://github.com/domenic/promises-unwrapping