Tri Dung Le dungletri

Problem: My Node.js processes (drones on Nodejitsu) are repeatedly growing in memory until they crash and get restarted. They are multiple processes responding to websockets connections over socket.io, using socket.io's Redis store to broker messages across connections and broadcast messages.

Conclusion: that socket.io's Redis store's memory usage likely either grows indefinitely, or is just way too high. We also isolated semi-frequent reconnects to the redis client on the part of each node.js process, though this looks unrelated to the overall memory problem.

Possibly related: socketio/socket.io#1040 socketio/socket.io#463

=== edited chat log of #nodejitsu on 25/11/2012 follows ==

	--log_gc (Log heap samples on garbage collection for the hp2ps tool.)
	type: bool default: false
	--expose_gc (expose gc extension)
	type: bool default: false
	--max_new_space_size (max size of the new generation (in kBytes))
	type: int default: 0
	--max_old_space_size (max size of the old generation (in Mbytes))
	type: int default: 0
	--max_executable_size (max size of executable memory (in Mbytes))
	type: int default: 0

	Tags: Sublime Text 2 License Key, Sublime Text 3 License Key, Sublime Text Full Version

	Go to menu Help > Enter License.


	----- BEGIN LICENSE -----
	J2TeaM
	2 User License
	EA7E-940282
	45CB0D8F 09100037 7D1056EB A1DDC1A2

	ruleset a8x72 {
	meta {
	name "NeoSale"
	description <<
	Selling the Neo Freerunner
	>>
	author "Sam Curren"
	logging on
	key twitter {
	"consumer_key" : "<redacted>",