Strange Segfault with SSL/TLS

We are experiencing a segfault with Node 4.3.2 under certain conditions.

The following code replicates it:

'use strict';

const Promise = require('bluebird');
const request = require('request-promise');

function thenHandler(options) {
  return request(options)
}

let options = {
  url: '/sdgasdnasodgnkn',
  method: 'GET',
  baseUrl: 'https://google.com'
};

Promise.resolve(options)
.then(thenHandler)
.catch(error => {
  console.log(error.response.socket);
  throw error;
});

Interestingly, removing thenHandler or using HTTP, not HTTPS, does not cause the error.

[wiggzz]

For future reference, it looks like this is the same issue which is fixed by this commit. Also, in order to patch in that change to 4.3, it seems possible to do something like:

const tls_wrap = process.binding('tls_wrap');
const old_close = tls_wrap.TLSWrap.prototype.close;
tls_wrap.TLSWrap.prototype.close = function(cb) {
  if (this.owner)
    this.owner.ssl = null;

  return old_close.apply(this, cb);
}

[wiggzz]

Yea. Would love to update but AWS Lambda is only supporting v4.3.2 and v0.10, so we’re kinda stuck on 4.3.2 until AWS decide to upgrade.