mudlet-makers team mailing list archive
-
mudlet-makers team
-
Mailing list archive
-
Message #04027
[Bug 1218614] Re: Temporary timers & triggers Lua code be marked for deletion after they've executed
Sadly, this prevents me from being able to use
function tempGag(time, line)
local trig = tempRegexTrigger(line, [[
deleteLine()
]])
tempTimer(time, [[killTrigger(]]..trig..[[)]])
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!!
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1218614
Title:
Temporary timers & triggers Lua code be marked for deletion after
they've executed
Status in Mudlet the MUD client:
New
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://forums.mudlet.org/viewtopic.php?f=7&t=3593 for the original
report.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1218614/+subscriptions
References