You need to capture the return value from setInterval( … ) into a variable as that is the reference to the timer: var interval; var count = 0; function onloadFunctions() { countUp(); interval = setInterval(countUp, 200); } /* … code … */ function countUp() { document.getElementById(“here”).innerHTML = count; count++; if(count === 10) { clearInterval(interval); countUp(); … Read more
Add a span element and update its text content. var span = document.getElementById(‘span’); function time() { var d = new Date(); var s = d.getSeconds(); var m = d.getMinutes(); var h = d.getHours(); span.textContent = (“0” + h).substr(-2) + “:” + (“0” + m).substr(-2) + “:” + (“0″ + s).substr(-2); } setInterval(time, 1000); <span id=”span”></span> … Read more
Be carefull.. your first code would block JavaScript event loop. Basically in JS is something like list of functions which should be processed. When you call setTimeout, setInterval or process.nextTick you will add given function to this list and when the right times comes, it will be processed.. Your code in the first case would … Read more
EDIT: Yury’s answer is better. tl;dr IMO there is no memory leak. The positive slope is simply the effect of setInterval and setTimeout. The garbage is collected, as seen by sawtooth patterns, meaning by definition there is no memory leak. (I think). I’m not sure there is a way to work around this so-called “memory … Read more
A lot of other answers are focusing on a pattern that does work, but their explanations aren’t really very thorough as to why your current code doesn’t work. Your code, for reference: function funcName() { alert(“test”); } var func = funcName(); var run = setInterval(“func”,10000) Let’s break this up into chunks. Your function funcName is … Read more
Change: setInterval(getMessages(), queryInterval); To: setInterval(getMessages, queryInterval);
Chrome (and apparently the latest versions of Firefox too) reduce the speed of setInterval when the tab is in the background to improve foreground performance. This probably matters the most when there are fast running timer-driven animations in background pages. When the page comes back to the foreground, it “tries” to catch up and runs … Read more
http://jsfiddle.net/wWHux/3/ You called the function immediately instead of passing it to setInterval. setInterval( change, 1500 ) – passes function change to setInterval setInterval( change(), 1500 ) – calls the function change and passes the result (undefined) to setInterval
You need to clear your interval, useEffect(() => { const intervalId = setInterval(() => { //assign interval to a variable to clear it. setState(state => ({ data: state.data, error: false, loading: true })) fetch(url) .then(data => data.json()) .then(obj => Object.keys(obj).map(key => { let newData = obj[key] newData.key = key return newData }) ) .then(newData => … Read more
From quick test, all major browsers (latest Chrome, Firefox and IE) give pretty small numbers as the ID so just looping “blindly” over all possible numbers should work just fine: function ClearAllIntervals() { for (var i = 1; i < 99999; i++) window.clearInterval(i); } Full example: window.onload = function() { window.setInterval(function() { document.getElementById(“Tick”).innerHTML += “tick<br … Read more