Bluebird unusable in AWS Lambda / NodeJS

1. What version of bluebird is the issue happening on? 3.4.7

2. What platform and version? (For example Node.js 0.12 or Google Chrome 32) NodeJS 4.3

3. Did this issue happen with earlier version of bluebird? Unknown

In an AWS Lambda function written in JS, using bluebird and executing on NodeJS:

1. a promise is created
2. on a setTimeout, the promise is resolved
3. when it’s resolved, the lambda function callback is invoked

IF the lambda function’s execution timeout occurs before the setTimeout, the internal state of the bluebird library is hosed, and not only does this invocation of the lambda function time out, but ALL FURTHER invocations of the lambda function fail by timing out.

Code below (sans node_modules needed for packaging as lambda fn). Note that the code below uses the input event’s .timeout property for the setTimeout.

var Promise = require("bluebird");

module.exports.hello = function(event, context, cb) {
    var p = new Promise(function(resolve, reject) {
        setTimeout(
            function() {
                resolve();
            },
            event.timeout);
    });
    p.then(function(foo) {
        cb(null, "cb happy");
    });
};

[simoncpu]

@truedat101 My bad, I isolated this issue on our code and turns out that this was related to ioredis, not Bluebird. The solution to prevent Lambda from timing out is at: https://www.linkedin.com/pulse/aws-lambda-reusable-resources-marjan-sterjev.

[cvillecsteele]

This is a WTF moment… No real problem with Bluebird… Seems to be an AWS/Lambda problem. Bumping up the RAM allocated to the lambda function makes everything better… Completely inexplicable. I’m opening up a ticket with AWS.