[go-nuts] NewTicker leak

2017-04-14 Thread Sokolov Yura
When you dereference pointer, you creates a copy at different address. But runtime internals stores pointer to original ticker, not your copy. So, call to Stop on your copy simply does nothing. All created tickers are alive and still sending ticks. -- You received this message because you are

[go-nuts] NewTicker leak

2017-04-14 Thread Sokolov Yura
Don't do this: t.ticker = *time.NewTicker(t.period) Never, never, never dereference anything you got from standard library by pointer. (And not only from standard library). -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe fro

[go-nuts] NewTicker leak

2017-04-13 Thread Fabián Inostroza
Hi, I'm writing and application where I need to check for some condition and do something every 'x' < 'y' seconds. If the condition is not true after 'y' seconds I do something. Every time the condition checked every 'x' seconds is true I have to reset the 'y' timeout. I wrote a test applicati