Timers are unreliable (firing too fast) when Dev Tools are open

[dzek69]

• Review the documentation: https://facebook.github.io/react-native
• Search for existing issues: https://github.com/facebook/react-native/issues
• Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

  React Native Environment Info:
    System:
      OS: Windows 10
      CPU: (8) ia32 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
      Memory: 2.97 GB / 15.89 GB
    Binaries:
      Node: 11.2.0 - C:\nodejs\node.EXE
      Yarn: 1.12.3 - C:\Apps\Yarn\bin\yarn.CMD
      npm: 6.4.1 - C:\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  3.2.0.0 AI-181.5540.7.32.5056338

Description

The same thing as here: #14639
Timers (both intervals and timeouts) are firing too fast, looks like they're dividing the time value by some factor.

Reproducible Demo

const start = Date.now();
console.log("start")
const fn = () => {
    console.log("end", Date.now() - start);
}

Simple setTimeout(fn, 5000) usually calls the function in around 1 second, but can be even faster.
Closing Dev Tools solves the issue.

#14639 seems to be wrongly closed by bot or there is an regression.

[konradkierus]

I'm having exactly the same issue but on Ubuntu and RN in version 0.57.5 - just for the info because if's different version of RN and system than the author.

[dzek69]

This is probably what causes #4944 (which is incorrectly closed or if it really was fixed then it should be reopened or something)

[ninofiliu]

I've got a similar issue SO link. #14639 was definitely wrongly closed. This issue needs to be resolved. Apps can't be built if basic time management functions don't work 😒

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.