Assertion failed: new_time >= loop->time

[Jan-Kruse]

• Version: 1.16.1
• Platform: Windows 7 64 Bit

Using latest node.js (libuv version 1.16.1) on my machine, causes the following error:
Assertion failed: new_time >= loop->time, file src\win\timer.c, line 37

I'm using a non overclocked AMD FX-6300. Yesterday it worked fine, but after a reboot it does not work anymore.

[bnoordhuis]

It means the system clock is drifting. It's not a libuv issue; libuv merely detects it and aborts.

You might be able to work around it by selecting a different clock source, e.g. ACPI instead of TSC (although I have no idea how you do that on Windows), or by tweaking settings in the BIOS.

[Jan-Kruse]

The issue was fixed by doing a CMOS reset on my system.

[refack]

@Jan-Kruse You might also want to check your onboard CMOS backup battery

[natewatson999]

I encountered this issue in an Amazon AWS EC2 Windows Server instance. I'm not sure if I can do a CMOS reset in that context.

[bnoordhuis]

@natewatson999 If nothing/no one touched the system clock then you should probably file an issue with AWS because that sounds like a bug.

[agarcian]

I am experiencing the same issue in an AWS EC2 Windows server. This is a long running job and it fails in Windows only.

[Jan-Kruse]

In my case my investigations showed, that using the X-Boost Feature of my ASRock main board caused this error in Windows. Maybe Amazon ist using a similiar feature in their server hardware. Which windows version are you on? Am 10.02.2018 um 22:19 schrieb Andres Garcia <notifications@github.com<mailto:notifications@github.com>>: I am experiencing the same issue in an AWS EC2 Windows server. This is a long running job and it fails in Windows only. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flibuv%2Flibuv%2Fissues%2F1633%23issuecomment-364693518&data=02%7C01%7Cjan.kruse%40utilitas.net%7C7cac491e117946e7904f08d570cc013f%7C29fc3f7b8d284065b2bfc24d2e10c116%7C1%7C0%7C636538943853760132&sdata=3e3N%2BitF1X%2Fi%2FsirKBOe5YUbmNccwCld0JK8sApo0Ng%3D&reserved=0>, or mute the thread<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARpcKabFMqC0FVxah27EnFU00FktwADJks5tTgfugaJpZM4QjVtN&data=02%7C01%7Cjan.kruse%40utilitas.net%7C7cac491e117946e7904f08d570cc013f%7C29fc3f7b8d284065b2bfc24d2e10c116%7C1%7C0%7C636538943853760132&sdata=c04W61RHns%2F59kg887a1DbMmHD4jpBGKXLx2WFeonmY%3D&reserved=0>.

[jdmayfield]

I am getting this on both node.js and nw.js on a Win7 VM inside virtualbox. I haven't seen it happen on the host, which is running on Linux Mint.

Is there a way to prevent this in my code? I'm trying to run a node-based Windows Service and this periodically crashes it.

[amoltivarekar]

• Version: 1.16.1
• Platform: Windows 7 64 Bit

Using latest node.js (libuv version 1.16.1) on my machine, causes the following error:
Assertion failed: new_time >= loop->time, file src\win\timer.c, line 37

I'm using a non overclocked AMD FX-6300. Yesterday it worked fine, but after a reboot it does not work anymore.

Hi, I'm facing same issue using react-native with expo , how can i fix it.. please help me.

[izk1989]

I am having the same issue, and i have the exact same cpu, non overclocked. Any solutions?
Assertion failed: new_time >= loop->time, file src\win\core.c, line 309t@1.2.0