Race condition when running the redis example about server HOT 4 CLOSED

Thanks @donstephan for reporting this!

The issue is *system.Info was passed into hooks, and in the Redis hook, it directly dereferenced the live info:

I have provided a fix in PR #365, please verify.

from server.

Issue is here:

go s.eventLoop() starts and the the s.publishSysTopics() runs right after it which could race with channels in the event loop. Would be very rare (if not impossible) to hit. If I'm reading it right, you'd somehow need a pause of 1 second between those two function executions to encounter this condition. Easiest fix is to just move the s.publishSysTopics() into the eventLoop() function so it runs before it listens to the tickers. Or it could just be moved above the eventLoop() execution in the server file.

from server.

Looks great. Tested the PR with the redis example and no more race. Thank you much!

from server.

@donstephan , this is incorporated into v2.4.6.

from server.