Change detection after error creating infinite loop

**I'm submitting a ...** (check one with "x") ``` [X] bug report => search github for a similar issue or PR before submitting [ ] feature request [ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question ``` **Current behavior** Possibly relates to #9531 and #16426. Since the change to continue change detection after an error (4.1.1), I'm getting an infinite loop of errors if there's a problem with template parsing (such as a bound variable doesn't exist). It causes the browser to completely hang, and the browser process must be manually killed. The console shows the infinite errors like this:  If I add a breakpoint in my error `handleError()` method, I can get a stack trace which may help with diagnosis. Since it is long, I'll attach it rather than embed. [angular error loop stacktrace.txt](https://github.com/angular/angular/files/1027943/angular.error.loop.stacktrace.txt) The issue is not my error handler triggering some sort of change detection, because I can completely remove the custom error handler class and the issue still manifests. If you look through the stack trace, you can see that everything going on is internal to Angular, SystemJS (maybe it keeps trying to make XHR calls to load files, which triggers change detection?), and/or Zone. I'm

Posted by brian428 on May 25, 2017, 4:25 AM

Tags

• support (Software)

Related issues

• Add 65536 size support for maps
• TypeScript 7.1 Iteration Plan
• nvim-treeconfig: upstream nvim-treesitter
• Add the "action" and "method" attributes to <button>
• [FEATURE] Support multiple Connector accounts (same connector, different accounts) in Claude and Claude Code on the web (claude.ai/code)
• > We were imposed GitHub for so many exercises!