Repository navigation
Callbacks called twice #25159
Description
- Version: 8.14.0
- Platform: 32-bit Windows
- Subsystem: timers or http
We were using 8.11.1 on production servers for some time now. After an update to 8.14.0 some of the server we started to receive below exception (only on the updated ones):
Error: Callback was already called.
at Timeout._onTimeout (D:\home\site\wwwroot\node_modules\async\lib\async.js:43:36)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
Async library checks if callback was fired twice which should not happen. The issue happens very rarely (once every 1-2 hours on one of many node processes handling 100 req/s), but sometimes it happens 3-4 times in a row in timespan of 100ms (the same node process). After reverting back to 8.11.1 issue is gone.
We cannot reproduce it locally to provide a sample test case. I assume it has to have something to do with recent security fixes and http module adding two setTimeouts or firing some event twice in case of http error/timeout (our node app is running in the cloud so this happens but rarely). I doubt that timer.js core module itself is the cause.
It may also be related to #23631, but there only 10.x is mentioned. We also do not think aby lib currently used by us refers to http2 module (only to http).
Activity
mritunjayz commentedon Dec 21, 2018
It seem like same as #23631 missed condition for 'false' value of 'self._writableState.errorEmitted' in If block.(line
node/lib/_tls_wrap.js
Line 481 in 187694e
'self._writableState.errorEmitted' have to be 'True' after each callback.
gluwer commentedon Dec 28, 2018
Sorry for the delay. Will this fix be backported to 8.x?
Trott commentedon Dec 28, 2018
@gluwer On the one hand, b94ce57 does not cherry-pick cleanly to the 8.x-staging branch. And it landed in October, so you'd think that if it was going to land in 8.x, it would have landed by now. So that suggests "no". However...
On the other hand, I don't see any
dont-land-ontags in #23631. And 8.x is in Active Maintenance for at least a few more days, if not a few more weeks. So a report like this one along the lines of "this is a bug that is affecting me" might warrant a backport?Ultimately, it's probably up to some combination of: @nodejs/releasers @nodejs/backporters @cjihrig
BridgeAR commentedon Jan 2, 2020
Node.js v8.x has reached the end-of-life and won't receive any fixes anymore. I am closing this since this issue only applies to Node.js v8.x. Other release lines received a fix.
No matter if you run into this issue or not, please update to a newer Node.js version in case you still use v8.x.