Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #25702 > unrolled thread

Chrome is stuck in "Prevent this page from creating additional dialogs"

Back to article view | Back to comp.lang.javascript

Contents

  Chrome is stuck in "Prevent this page from creating additional dialogs" sethhubert1@gmail.com - 2014-08-17 13:51 -0700
    Re: Chrome is stuck in "Prevent this page from creating additional dialogs" Mike Duffy <md_002@videotron.ca> - 2014-08-17 17:30 -0400
      Re: Chrome is stuck in "Prevent this page from creating additional dialogs" sethhubert1@gmail.com - 2014-08-17 15:34 -0700
        Re: Chrome is stuck in "Prevent this page from creating additional dialogs" Denis McMahon <denismfmcmahon@gmail.com> - 2014-08-18 00:31 +0000
    Re: Chrome is stuck in "Prevent this page from creating additional dialogs" "J. Clarke" <jclarkeusenet@cox.net> - 2014-08-17 21:10 -0400
    Re: Chrome is stuck in "Prevent this page from creating additional dialogs" sethhubert1@gmail.com - 2014-08-17 19:32 -0700

#25702 — Chrome is stuck in "Prevent this page from creating additional dialogs"

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
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!!!

How do I escape this??

[toc] | [next] | [standalone]

#25703

On Sun, 17 Aug 2014 13:51:35 -0700 (PDT), sethhubert1@gmail.com wrote:

> How do I escape this??

Abort it using "task manager".
De-install.
Re-install.

If it doesn't work, do it again, but destroy/recreate the user profile
before the re-install. This will destroy any user settings for a variety of
programs, so back up anything important first.

-- 
http://pages.videotron.ca/duffym/index.htm

[toc] | [prev] | [next] | [standalone]

#25704

You're missing the extent of the problem. I can quit Chrome with no problem, but the loop continues!

Even if I stop Nodejs server
Even if I stop all programs and reboot!

I edited the code to do nothing, then re-booted, and the problem persists!

Something is 'caching' this 'process,' but I don't know what that is, or where I can  make changes.

[toc] | [prev] | [next] | [standalone]

#25705

On Sun, 17 Aug 2014 15:34:16 -0700, sethhubert1 wrote:

> Something is 'caching' this 'process,' but I don't know what that is, or
> where I can  make changes.

Chrome may have the page cached somewhere. Quit chrome, find the cache 
and delete everything in it.

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#25706

In article <6c585547-5723-4c4c-902a-a2ea84055859@googlegroups.com>, 
sethhubert1@gmail.com says...
> 
> 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
> 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!!!
> 
> How do I escape this??

It appears that you have a copy of your script in either the node or 
chrome cache folders.

The easy thing to try is "Chrome --home" from a command line, which 
should start Chrome without reloading the previous session.  You may 
have to specify the full path to chrome or change directory into the one 
in which it is installed.  

You can also look into temporarily changing the cache locations to empty 
folders using the "--disk-cache-dir=" and "--media-cache-dir=" command-
line parameters for Chrome and "npm config set cache" for node.

If that doesn't work, you might want to locate and clear both caches and 
see what happens.  You don't say what OS you're running--under Windows 
the node.js cache is normally in "%APP_DATA%\npm-cache" and the Chrome 
cache is normally in 
"%APP_DATA%\Local\Google\Chrome\User Data\Default\Cache".  You may have 
to go into folder options and turn on "view hidden folders" or whatever 
it's called on your version of Windows to get there.  If you're not 
running Windows, then grep for some of the code in your script and you 
should be able to find where the cached copy is being stored.

[toc] | [prev] | [next] | [standalone]

#25707

@J. Clarke +3

Muchas Gracias! THis is really good information. Thanks VERY much!!!

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web