Chrome is probably cache-ing your page or something like that. Or you've not actually deleted the loop- maybe you deleted it from a coffeescript / ES6 file and didn't actually do your build process on it?
Or maybe the error is somewhere else. Can you just launch chrome in general? Can you do a curl command to get the relevant files and see what your node server is serving up? e On Sun, Aug 17, 2014 at 2:42 PM, Seth Hubert <[email protected]> wrote: > I'm not sure which technology is the root of this problem. Please forgive > me if it is not an AngularJS problem. > >>> > I made the mistake of using the alert() function in a loop of 25,000 > steps, and have checked the "Prevent this page from creating additional > dialogs" checkbox. > > Chrome will not quit processing the loop, even if I reboot the machine! > > I reboot, and then: > Delete the loop and alert from my code > Start Nodejs server > Start Chrome and load my AngularJS webpage > > It is STILL in the loop of code that has been deleted AFTER reboot!!! > > I don't see any Chrome setting to change, and Google searches are drawing > no references to Node or Angular. > > How do I escape this?? > > Anyone?? > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
