-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Closed
Description
Very simple code. SIngle connection eats memory.
Node 0.8.14. Socket..io 0.9.10
Server:
var
io = require('socket.io').listen(3000,{
transports:[
'websocket',
'htmlfile',
'xhr-polling',
'jsonp-polling'
]
});
io.sockets.on('connection',function(socket){
socket.on('ping',function(){
socket.emit('pong');
});
});Client:
<head>
<script src="http://localhost:3000/socket.io/socket.io.js"></script>
<script>
var socket = io.connect('http://localhost:3000');
function ping(){
socket.emit('ping');
}
socket.on('pong',ping);
ping();
</script>Tested under Windows. Run server, run client - see in task manager how node.exe eats memory.
Comment transports in server. Websocket and jsonp-polling leak. xhr-polling - does not.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels