Console logs "Booting Client" around 100 times, then crashes.

I have a bug(?) with my node.js. And I think it has something to do with socket.io. So what it does is Logging "Booting Client" around a hundred times, then it crashes with the error:

util.js:35 var str = String(f).replace(formatRegExp, function(x) { ^ RangeError: Maximum call stack size exceeded

I am guessing that the stack size is exceeded because Socket.io is doing "booting client" so many times.

[3rd-Eden]

There is no such string as "Booting Client" in the socket.io source code

Then it might be nodejs itself... I'll repost the Issue there

I found out that it acctually does contain "booting client" under node_modules/socket.io/lib/socket.js
What proves that it is an issue with socket.io.

The code where it does that is line 290 to 310:
Socket.prototype.disconnect = function () {
if (!this.disconnected) {
this.log.info('booting client');

if ('' === this.namespace.name) {
  if (this.manager.transports[this.id] && this.manager.transports[this.id].open) {
    this.manager.transports[this.id].onForcedDisconnect();
  } else {
    this.manager.onClientDisconnect(this.id);
    this.manager.store.publish('disconnect:' + this.id);
  }
} else {
  this.packet({type: 'disconnect'});
  this.manager.onLeave(this.id, this.namespace.name);
  this.$emit('disconnect', 'booted');
}

}

return this;
};

[3rd-Eden]

Oh good catch, it seemed that my files where out of date :p

Good, I hope we can fix this now. It really is slowing down my development.

I have an idea what it might be:
This function calls when the client disconnects doesnt it?
And in the function there is:
this.$emit('disconnect', 'booted');
and
this.manager.store.publish('disconnect:' + this.id);

Which basically(at least to my understanding) disconnect the client.

So when the function is called, it disconnects the client, what calls it again.

Also this only happens since my newest update in ym game, and I remember including the 'socket.on("disconnect"'
there... This might be it. I'll remove that event and see if it still does it once I get back to development.

Seems like it was my fault (Stupid idiot me). I had put socket.disconnect() in the socket.on("disconnect") event thinking that it would call it only once, stupid stupid me. Changed it to socket.once("disconnect") now. Sorry for wasting your time.

[sivatumma]

I am kind of not satisfied with this answer. Mine is a similar issue, Help if you can find some answer...
Here is my code

var app = require('express')();
var server = require('http').Server(app);
var io = require('socket.io')(server);

io.on('connection', function(socket) {
  console.log("Client connected through 'connect' socket.io ");
  socket.emit('data',{siva:"is thumma"});

  var server = require('net').createServer(function(deviceSocket) {
    deviceSocket.on('data', function(data) {
      var decodedDeviceData = data.toString('utf8');
      console.log("Data from client", data);
      deviceSocket.emit('data',data);
      deviceSocket.emit('data', decodedDeviceData);

    });
  });
  server.listen(5062, "0.0.0.0");
});