Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Out of stack space" - karma with IE11 and webpack #143

Closed
dballance opened this issue Dec 14, 2015 · 6 comments
Closed

"Out of stack space" - karma with IE11 and webpack #143

dballance opened this issue Dec 14, 2015 · 6 comments

Comments

@dballance
Copy link

Getting the following in IE11 on Windows10 using angular2-webpack-starter and karma-ie-launcher.

IE 11.0.0 (Windows 10 0.0.0) ERROR
  Out of stack space
  at C:/angular2-webpack-starter/spec-bundle.js:1064 <- webpack:///~/core-js/modules/es6.symbol.js:54:0

Offending lines:

 set: function(value){
      if(has(this, HIDDEN) && has(this[HIDDEN], tag))this[HIDDEN][tag] = false;
      setSymbolDesc(this, tag, createDesc(1, value));
 }

Removing / commenting the set descriptor function appears to resolve the issue.

 set: function(value){
      //if(has(this, HIDDEN) && has(this[HIDDEN], tag))this[HIDDEN][tag] = false;
      //setSymbolDesc(this, tag, createDesc(1, value));
 }

PhantomJS and Chrome tests run fine, only IE with this issue. Not sure how to resolve --- it seems to be calling the set method with enough iterations to overflow the stack.

@dballance
Copy link
Author

Forgot to add -- possibly related to #96 but unsure how to resolve with webpack + Typescript.

@zloirock
Copy link
Owner

Please, write a simple reproducible example.

@zloirock
Copy link
Owner

@dballance any news about a reproducible example? I don't see the problem just in karma + IE11 + webpack, so looks like this problem in your config.

@dballance
Copy link
Author

I haven't had any time to provide a repro for this. It most likely is in my config - will close and provide a repro if it pops up again and I have time to investigate.

@BenGWeeks
Copy link

Let me know if you want access to a URL to see this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants