Always on status causing panic #2113
Description
We are using ergochat as the chat server for our game client. We have recently been experimenting with using the always-on functionality to enable offline messages for our player base.
After enabling always on we have noticed that the chat server occasionally dies from an invalid memory address when trying to update the status of one of the users. This was occurring when there were approximately 1k users both offline and online.
I tried to search the documentation to see if there were any caveats related to the always-on status but was not able to find anything. If you have any ideas or suggestions on how this possibly could be resolved that would be greatly appreciated.
We are using ergochat 2.12.0 running in docker.
ergochat_1 | panic: runtime error: invalid memory address or nil pointer dereference
ergochat_1 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7b3cb0]
ergochat_1 | goroutine 151577592 [running]:
ergochat_1 | github.com/ergochat/ergo/irc.(*Channel).alwaysOnStatus(0xc0218a9500?, 0x7fc113dd8640?)
ergochat_1 | /go/src/github.com/ergochat/ergo/irc/channel.go:553 +0xd0
ergochat_1 | github.com/ergochat/ergo/irc.(*Client).performWrite(0xc0218a9500, 0x0)
ergochat_1 | /go/src/github.com/ergochat/ergo/irc/client.go:1806 +0x1af
ergochat_1 | github.com/ergochat/ergo/irc.(*Client).writeLoop(0xc0218a9500)
ergochat_1 | /go/src/github.com/ergochat/ergo/irc/client.go:1777 +0x1e
ergochat_1 | created by github.com/ergochat/ergo/irc.(*Client).wakeWriter in goroutine 151614265
ergochat_1 | /go/src/github.com/ergochat/ergo/irc/client.go:1771 +0x99