-
Notifications
You must be signed in to change notification settings - Fork 408
long-stack-trace throws error in InternetExplorer #698
Comments
@Eddman , do you have a reproduce repo? thank you. |
Well not exactly easy to reproduce. I have 260+ Karma tests and it fails after few minutes. The exception seems to break the whole Karma run. So I'm even not able to detect what test it is. When I remove The application itself seems to work correctly. The only problem is the one test. |
@Eddman , could you help to debug the error.originalStack property when the error occurs? |
Just put there |
One more: The error that is causing it is: |
@Eddman, Thank you for the information, if you can provide the error test case code snippet will help, and you are using IE11? And can you post your polyfill file (core-js)? |
You can use the commit linked above. I'm not able to make a smaller scenario. It only fails when all tests are executed. I'm using IE 11 + Win 7. Please run Chrome and FF are running fine. As polyfill I use |
@Eddman , thank you, I will test it. |
@Eddman , I tried your repo, but I don't know how to reproduce.
this is the result. |
We see the same issue in Angular tests (IE9): https://travis-ci.org/angular/angular/jobs/216434920#L565 |
@JiaLiPassion Could you have a look? |
@mhevery, sure, I will check it. |
@JiaLiPassion Use the commit https://github.com/Deutsche-Boerse-Risk/DAVe-UI/commit/c292aaf4c19d218cd6b300a0fb7e997126bb23cc, not the latest one. |
@Eddman, thank you, I can reproduce now, I will debug it. |
@Eddman, I have found the reason, this is a trick one, the reason is because Error.stackTraceLimit is set to 0 in karma-test-shim, I will make a PR to fix it, thank you for your great help. |
…rror.stackTraceLimit = 0, add null check
…rror.stackTraceLimit = 0, add null check
…rror.stackTraceLimit = 0, add null check
…rror.stackTraceLimit = 0, add null check
Error.stack is sometimes
undefined
in IE. Therefor Zone fails to call trim method on it:zone.js/dist/long-stack-trace-zone.js
Line 70 in e11d9ff
The text was updated successfully, but these errors were encountered: