value is stale in the event handler because it gets its value from the closure where it was defined. Unless we re-subscribe a new event handler every time value changes, it will not get the new value. Solution 1: Make the second argument to the publish effect [value]. This makes the event handler get the … Read more
It turns out that this is a bug in nodejs core, we are talking about this problem here : https://github.com/joyent/node/issues/5108 Solution for bugged http servers thats throw an EventEmitter memory leak detected and fill up the available memory / available CPU times : Revert to legacy version v0.8.23. (You can download and install/compile it from … Read more
I’d like to point out here that that warning is there for a reason and there’s a good chance the right fix is not increasing the limit but figuring out why you’re adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and … Read more
Update 2016-06-27: instead of using Observables, use either a BehaviorSubject, as recommended by @Abdulrahman in a comment, or a ReplaySubject, as recommended by @Jason Goemaat in a comment A Subject is both an Observable (so we can subscribe() to it) and an Observer (so we can call next() on it to emit a new value). … Read more