[g37752]

if it continues to run, your computer might become unresponsive.

what's wrong in this code that is causing this warning? (i did not have a problem without the while loop.)

$(document).ready(function(){
	waitForUpdate(); 
    while(1==1)
    {
		var d=new Date();
		m=d.getMinutes();
		sec=d.getSeconds();
    	if((m%10)==0 && sec>20){
    		setTimeout(waitForUpdate(),60000);     			
    	}
    }
});

[raghav.naganathan]

Well, as you mentioned, that while loop is responsible for causing the problem.

Well, you are looping infinite times...as 1 will always be equal to 1...and there is no loop exit condition.

regards,
Raghav

[g37752]

i know its an infinite loop, nut i wait 10 min.

[Dormilich]

there is also a problem with the setTimeout(). you don’t wait 10 mins before the next waitForUpdate() is executed, because you execute that function each time you call setTimeout(). in other words, you tell setTimeout() to execute nothing (i.e. undefined) every minute. reason: setTimeout() expects a function to be given, not a function return value. i.e. it should be setTimeout(waitForUpdate, 60000);

[g37752]

i now suspect the problem is not setTimeout (except for the syntax problem). i did wait 10 minutes to call setTimeout.

I think the cpu is busy because i keep evaluating the current time. i still couldnt find a solution to this.

what i am trying to do is to update client browsers every 10 minutes at specific times e.g., 5:10, 5:20, 5:30, etc.

[g37752]

my workaround got rid of the problem, but i got "unspecified error?"

function areWeThereYet()
{
	var d=new Date();
	m=d.getMinutes();
	sec=d.getSeconds();
	if((m%10)==0 && sec>20){
		setTimeout(waitForUpdate,600000);  			
	}
}

$(document).ready(function(){
    waitForUpdate(); 
    while(1==1)
    {
    	setTimeout(areWeThereYet,60000);  
    }
    
});

hmm.. i did miss a '0' in wait time..

This post has been edited by g37752: 22 February 2013 - 05:25 PM

[andrewsw]

The code within while (1==1) is going to run and run. It will be setting the timeout, but the loop continues to run, eating up the CPU.

If you want to call a function at a regular interval you might remove the while loop and just use setInterval.

[g37752]

andrewsw, on 22 February 2013 - 03:43 PM, said:

The code within while (1==1) is going to run and run. It will be setting the timeout, but the loop continues to run, eating up the CPU.

If you want to call a function at a regular interval you might remove the while loop and just use setInterval.

so i change this:

    while(1==1)
    {
      setTimeout(areWeThereYet,600000); 
    }

to this:

setInterval(areWeThereYet,60000);

and the unspecified error is gone. i thought they should work the same?

[Dormilich]

g37752, on 23 February 2013 - 01:24 AM, said:

i thought they should work the same?

not at all. you infinte while() loop runs very fast, and in each cycle (in less than a millisecond) it adds the waitForUpdate() function to the timeout stack. so when the first waitForUpdate() function would be executed after ten minutes, you would have a couple of billion functions in the stack waiting to be executed, which most probably have eaten your resource way before that point. besides that your browser will be in a lock, because it cannot execute the functions while the loop is still running.