Wednesday, 15 August 2012

node.js - Node (memory leak, v8 snapshot) - is it bad practice to use a connection promise? -



node.js - Node (memory leak, v8 snapshot) - is it bad practice to use a connection promise? -

i didn't want db requests run accidentally before connection, connect method returns promise , every single db method uses connectpromise.then().

it seems app leaking memory, i'm wondering if cause. top offender in v8 heap memory snapshot titled sql , contains lot of stuff bluebird promises , domains. don't know create of it, 1 single connect promise came mind.

edit: have confirmed source of problem indeed practice of keeping around promise sequelize. sake of testing, tried refreshing promise every 30 seconds , application stopped gathering more , more memory.

i have opened issue in sequelize

node.js memory-leaks garbage-collection sequelize.js bluebird

No comments:

Post a Comment