907402 - setInterval stops firing callback

Status: RESOLVED WORKSFORME

(Core :: Widget: Win32, defect)

Description

[Kastor]

Attachment: setInterval stops firing callback.html

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130814063812

Steps to reproduce:

created a setInterval with a timeout of 0.


Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0


Actual results:

setInterval fired a few times and then stopped on its own.


Expected results:

The interval should keep firing until I stop it myself or leave the page.

Comment 1

[Paul Silaghi, QA [:pauly]]

(In reply to Kastor from comment #0)
> setInterval fired a few times and then stopped on its own.
Cannot reproduce on FF 23.0.1, 26.0a1, still working after 5 min.

Please check if the issue occurs using Firefox in safe mode (with your addons disabled):
http://support.mozilla.com/kb/Safe+Mode

Or on a new, empty profile:
http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager

Comment 2

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

I was able to observe this problem twice on my dad's laptop using the URL. I believe this to be the cause of Bug 912521.

I did not yet have him try with a clean profile or safe mode. Will do that next time I talk to him.

Comment 3

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

I forgot the important point: With the URL, when the stream of numbers stopped (which happened twice), moving the mouse made them go again.

Comment 4

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Seems like there are other issues filed of this nature, related to bug 633421.

Comment 5

[Kastor]

I've been playing with this a bit and noticed that it always stops in the firebug console. When I use the built in console from web developer tools the problem is intermittent.

Comment 6

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

In our case we observed it in the built-in web console from web developer tools.

Comment 7

[Boris Zbarsky [:bzbarsky]]

> moving the mouse made them go again.

Sounds like the timer events never even got delivered to the DOM code for some reason...  Was this on Windows?

Comment 8

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

It was on Windows 7, yes. Bug 912521 has a crash-report with full system info (because it crashed in the flash code while doing STR on one occasion only. The crash seems less important).

Comment 9

[Boris Zbarsky [:bzbarsky]]

Sounds like a possible Windows event loop issue.  :(

Comment 10

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

(In reply to Jan-Ivar Bruaroey [:jib] from comment #2)
> I was able to observe this problem twice on my dad's laptop using the URL. I
> believe this to be the cause of Bug 912521.

I tried this again on my dad's laptop and it now works, and we can no longer reproduce it. Since he still experiences symptoms in bug 912521, I'm removing that dependency. Must be something else.

Comment 11

[Tracy Walker [:tracy]]

(In reply to Jan-Ivar Bruaroey [:jib] from comment #10)
> (In reply to Jan-Ivar Bruaroey [:jib] from comment #2)
> > I was able to observe this problem twice on my dad's laptop using the URL. I
> > believe this to be the cause of Bug 912521.
> 
> I tried this again on my dad's laptop and it now works, and we can no longer
> reproduce it. Since he still experiences symptoms in bug 912521, I'm
> removing that dependency. Must be something else.

I am also unable to reproduce.  Tested with latest Nightly 50.0a1, 
20160720030208 on Win 7