TLSSocket.destroy() is not fully closing the socket

[user447463]

io.js (along with node 0.12) seems to have introduced a timeout related issue for the TLS package. Closing the TLSSocket is not enough to stop the timeout but an additional TCP socket close is necessary.

Please see the following code sample for a reproducible pattern

var url=require('url').parse(process.argv[2]);
var secure=url.protocol=='https:';

var socket=new require('net').Socket();

socket.setTimeout(2000, function() {
    this.destroy();
    console.log('TCP connection timed out');
});

socket.connect({ host: url.hostname, port: url.port || (secure?443:80) }, function() {
    if (secure)
    {
        require('tls').connect({ socket: this, rejectUnauthorized: false, servername: url.hostname }, function() {
            this.destroy();
            console.log('SSL successfully connected');
        }).on('error', function(error){
            this.destroy();
            console.log('Error during SSL handshake');
        });
    }
    else
    {
        this.destroy();
        console.log('Non-SSL successfully connected');
    }
}).on('error', function(error) {
    this.destroy();
    console.log('Error during TCP connection '+error.code);
});

// Dummy line to keep node from exiting
setInterval(function() {}, 1000);

Expected result

iojs file.js https://www.google.com
SSL successfully connected

Actual result

iojs file.js https://www.google.com
SSL successfully connected
TCP connection timed out

[user447463]

The issue is reproducible with all available io.js versions (1.x). As it was not present in node.js until version 0.11.3 (respectively 0.12 in release-terms) I presume io.js itself is based on a post-0.11.2 version, correct?

[user447463]

For cross-reference, the respective bug at node.js
nodejs/node-v0.x-archive#9242

[user447463]

Appears to have been fixed in node.js