Is there a problem with this code？

[JsonDalao]

Look at this code,There are 100 leaks, right?

 

[Pyrogasm]

Yes because you are not destroying the timers. Unless you are using some sort of auto-destroying Lua stuff.

 

[JsonDalao]

Yes because you are not destroying the timers. Unless you are using some sort of auto-destroying Lua stuff.

If I destroyed it,Whether there is still a callback or event leak?

 

[Pyrogasm]

First I noticed that it's the same timer being started i times; I thought it was multiple different timers. The way you've written it the timer will ultimately only be started for 100s once and only expire that one time.

If I destroyed it,Whether there is still a callback or event leak?

I'm not really sure I understand what you're saying. The object itself needs to be destroyed, either in the callback or some other function that runs after the callback.

 

[Wrda]

Pyrogasm is correct. This loop is useless by its current state, you destroy the timer in the callback (or in a function in callback), doing it outside would just prevent it from doing anything in the callback.

TimerStart(t, i, false, function()
--do stuff
call DestroyTimer(t)
set t = nil --not sure if you actually need to null local variables in lua
end)

 

[Pyrogasm]

not sure if you actually need to null local variables in lua

One does not have to.