angular + requirejs: Quick refreshing pages cause page stop working in chrome

[caoglish]

during the development with angular + requirejs. I met a weird problem.

if I quick refresh page(like pressing F5), after a few times, I will get the following error message and the page is not working any more even refresh the page again, unless clean the cache and open the page on new tab:

Error: $digest already in progress
    at Error (<anonymous>)
    at beginPhase (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:8495:15)
    at Object.Scope.$apply (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:8297:11)
    at done (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9357:20)
    at completeRequest (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9520:7)
    at XMLHttpRequest.xhr.onreadystatechange (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9490:11)
    at http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9499:11
    at sendReq (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9333:9)
    at $http (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9124:17)
    at Function.$http.(anonymous function) (http://www.caoglish.info/angular_bug/assets/vendor/angular/angular.js:9267:18) 

this error seem to only happen in chrome on fast computer. I try to trigger it on IE and Firefox, it was not happening. however, I try it in chrome on slow computer, it also not happen.

the computer which I triggered this issue has i7 cpu, 8gb ram. angular I using is 1.0.8.

I attached my code which isolated this issue. my project code is more complex then this, so less times to trigger it. the isolated code may requires press more few times on F5 to trigger the issue.

the isolated example code: Link

how to trigger the bug: video

quick pressing F5 until it happen.

I create a stack overflow question in: Link

[caitp]

I have not been able to reproduce on my macbook, however I encounter this when refreshing during pageload, jshinting your sources might offer some help.

That said, the issue tracker is not really an appropriate place for support questions, the mailing list is more appropriate for that.

[caoglish]

I update my isolated code with Jshint checked. I still has the issue.

The error is on angular. The loading angular.js is successful. so I think this is a issue of angular.

I notice any javascript will show error that when loading processing have been stopped before page(or js file) fully loading. if you quick refreshing F5, you can see the error will show on the console before page refreshed. I think will I click F5 and the loading processing just at loading angular.js. when other JS scripts have error showing in this way, browser only need to refresh and the error will not show the error in next fully loaded page. however, angular show the same error in next fully loaded page. this is my theory of this.

[btford]

The links 404, and this doesn't seem like an issue with Angular but rather with how you've configured Require.js.

If you can post a minimal example on the latest version of Angular ( 1.2.7 ), then I'll happily reopen this.

Thanks!