http://redmine.emweb.be/http://redmine.emweb.be/favicon.ico?16934085252020-02-05T08:57:37ZRedmineWt - Bug #7440: WTimer results in excessive browser CPU and memory usage when connection is losthttp://redmine.emweb.be/issues/7440?journal_id=248592020-02-05T08:57:37ZRoel Standaertroel@emweb.be
<ul></ul><p>10ms is of course a very short interval, but I trust that is just to demonstrate?</p>
<p>I think it could be valuable to have some sort of last resort handling of situations like this (server is not responding, and we're accumulating many events).</p>
<p>Specifically in your case, you may want to just use a single shot timer that is restarted every time it times out. That way there can never be more than one timeout event.</p>
<p>What I would generally recommend if you want to trigger updates (that originate from the server) is to use server push to do so, either when an event that has to update the interface happens, or by using a server side timer (<code>WIOService::schedule</code> or <code>WServer::schedule</code> (the latter appears to be currently undocumented) could be used for that).</p>