Temporary timers & triggers Lua code be marked for deletion after they've executed
Bug #1218614 reported by
Vadim Peretokin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mudlet |
Opinion
|
Undecided
|
Unassigned |
Bug Description
Temporary timers & triggers Lua code should be marked for deletion after they've executed. Lua's incremental GC will account for actually deleting them in bits as it's necessary, so it will not be a performance hit (just like it hasn't been already for many user scripts).
The current setup creates a memory leak.
See http://
summary: |
- Temporary timers should be marked for deletion after they've executed + Temporary timers & triggers Lua code be marked for deletion after + they've executed |
description: | updated |
To post a comment you must log in.
Sadly, this prevents me from being able to use
function tempGag(time, line) r(line, [[ ]]..trig. .[[)]])
local trig = tempRegexTrigge
deleteLine()
]])
tempTimer(time, [[killTrigger(
return trig
end
until this bug is resolved, otherwise I end up having a 500mb memory usage and the game slows down unplayably.
The idea was to save time by having gag lines only considered shortly after the command that prompted their need was issued.
Please fix!!