Queued write requests should be invoked on handle close, otherwise the "consumer" might be already destroyed when the write callbacks of the "consumed" handle will be invoked. Same applies to the shutdown requests. Make sure to "move" away socket from server to not break the `connections` counter in `net.js`. Otherwise it might not call `close` callback, or call it too early. Fix: https://github.com/iojs/io.js/issues/1696 PR-URL: https://github.com/nodejs/io.js/pull/1910 Reviewed-By: Trevor Norris <trev.norris@gmail.com>
29 lines
553 B
JavaScript
29 lines
553 B
JavaScript
'use strict';
|
|
var assert = require('assert');
|
|
var common = require('../common');
|
|
|
|
if (!common.hasCrypto) {
|
|
console.log('1..0 # Skipped: missing crypto');
|
|
process.exit();
|
|
}
|
|
var tls = require('tls');
|
|
var stream = require('stream');
|
|
|
|
var delay = new stream.Duplex({
|
|
read: function read() {
|
|
},
|
|
write: function write(data, enc, cb) {
|
|
console.log('pending');
|
|
setTimeout(function() {
|
|
console.log('done');
|
|
cb();
|
|
}, 200);
|
|
}
|
|
});
|
|
|
|
var secure = tls.connect({
|
|
socket: delay
|
|
});
|
|
setImmediate(function() {
|
|
secure.destroy();
|
|
});
|