Merge pull request #127 from TG1999/development

Memory leakage tracking issue solved

Author: iamgrawal

READMEassets/Home.jpg

@@ -19,6 +19,7 @@
     "mongodb": "^3.1.0",
     "mongoose": "^5.1.7",
     "node": "^10.5.0",
+    "node-memwatch": "^1.0.1",
     "nodemon": "^1.18.8",
     "passport": "^0.4.0",
     "passport-facebook": "^2.1.1",

READMEassets/Info.png

@@ -13,6 +13,9 @@ const secret=require('./config/credential.js');
 const notification = require('./schema/notification.js');
 const indexRoutes = require('./routes/index.routes');
 const facebook = require('./config/facebook.js');
+var memwatch = require('node-memwatch');
+//Snapshot at start
+var hd = new memwatch.HeapDiff();
 
 mongoose.connect(secret.database, function () {
     console.log('connected');
@@ -32,8 +35,24 @@ app.use(passport.initialize());
 app.use(passport.session());
 
 app.use(indexRoutes);
-
-
+//Snapshot after routing
+var diff = hd.end();
+//Diff between both snapshots
+console.log(diff)
+//checking for leak in memory
+memwatch.on('leak',(info)=>{
+    for(x in info)
+    {
+        console.log(x+':'+info[x]);
+    }
+});
+//Stats of memory leakage
+memwatch.on('stats',(info)=>{
+    for(x in info)
+    {
+        console.log(x+':'+info[x]);
+    }
+});
 
 
 var ser = app.listen(3000, function () {