Given the number of known overflows present in the `time` package (https://go.dev/issue/20678, https://go.dev/issue/56909), I wouldn't be terribly surprised to find one in Ticker as well, although 6 months seems awfully short to hit an overflow bug.
Consider filing an issue at https://go.dev/issue/new. (Perhaps the runtime team can give you some advice there on how to collect a core dump for inspection?) On Sunday, November 26, 2023 at 4:59:10 PM UTC-5 Ari Croock wrote: > Hi, > > I hope someone here can shed some light on a problem I'm having. > > There is a detailed explanation on my stackoverflow question: > https://stackoverflow.com/questions/77538297/why-does-my-time-ticker-work-fine-for-6-months-then-suddenly-stop-sending-ticks > > The summary is I have a very simple time.Ticker running with a period of > 24h which calls a function that normally only takes a few seconds to run. > This worked perfectly fine for about 6 months but then suddenly stopped > working (the program has been continuously running for 6 months). > > I have attached the debugger so I can see it has paused execution on the > `select` statement, waiting for a value on the ticker channel. There > doesn't seem to be any way that the ticker.Stop method was called anywhere. > If anyone has any suggestions for things to look for in the debugger that > would be very welcome. > > The binary was built using "go version go1.21.4 linux/amd64". > > Thanks > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/6929318c-e57f-4643-aa1d-3f1e372f254en%40googlegroups.com.
