When I see this right this was fixed in v5.9.0
, see this PR. It appears that in those cases both node
core maintainer nor programmers can do much - that we pretty much have to wait for a upstream fix in v8
.
So no, you can't do anything more about it. Catching this bug was good though!