Hi Seth,
Not really enough information to go on.
Might be able to redefine alert to throw an error. To do this you want to
set a break point before any of the code runs and then run the below code
from the console. After continuing you should see stack traces in the
console.
window.alert = function(){ throw new Error('Fake alert');}
Hope that helps
On Monday, 18 August 2014 09:31:18 UTC+12, Seth Hubert wrote:
>
> I don't know if this problem is rooted in: Javascript, Chrome browser,
> AngularJS, or Nodejs
> Please forgive me if it not NodeJS's fault :)
> >>>
> I made the mistake of using the Javascript 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
> 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!!!
>
> Is NodeJS 'caching' the 'process' - I have no idea what to call the
> problem, or where it resides.
>
> Anyone??
>
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/27f426a8-8528-4067-a91e-4bfccadfa1e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
