setImediate callback not called

[pepone]

we are using the core-js setImediate included by babel-polyfill we are observing that with safari some times but not always the callback pass to setImediate is not dispatched

We are observing this in a large application and have non been able to track it down to a more simple test case, we added a workaround to use setTiemout with safari workers, and it solves our issue, but will be nice to track this down.

https://github.com/zeroc-ice/ice/blob/f44f04e79537e45ba28f61317d7233ee19f05313/js/src/Ice/browser/TimerUtil.js#L64-L71

[JakeChampion]

Have you tried replicating the issue by having a worker which only contains core-js and setImmediate?

[zloirock]

What's the version of Safari?

[zloirock]

I remember the same problem for microtasks in Safari, but not for tasks.

[pepone]

@zloirock that is with Safari 12.0.1 build 14606.2.104.1.1
@JakeChampion I didn't try

[pepone]

So far I have been testing an alternate implementation based on MessageChannel and works fine with the same Safari version

https://github.com/zeroc-ice/ice/blob/145d53a7cdb489a95178d7e6be95d98f16596e75/js/src/Ice/browser/TimerUtil.js#L89

[zloirock]

@pepone core-js should use the same in Safari.

[zloirock]

Maybe you also implicitly use another setImmediate polyfill which overrides core-js implementation?

[pepone]

core-js should use the same in Safari.

Yes I know, I looked at the implementation before and didn't see anything wrong there, we are observing the callback is not called with Safari but not always

Maybe you also implicitly use another setImmediate polyfill which overrides core-js implementation?

I don't think so, I will try to create a test with only the core-js implementation, we are getting this from babel polyfill that as far as I know uses core-js

[zloirock]

Closed as can't reproduce.