Temporary timers & triggers Lua code be marked for deletion after they've executed

Bug #1218614 reported by Vadim Peretokin
10
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://forums.mudlet.org/viewtopic.php?f=7&t=3593 for the original report.

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
Revision history for this message
asdfghjk (norehogasl) wrote :

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!!

Revision history for this message
Vadim Peretokin (vperetokin) wrote :

Migrating issues to Github, please follow the new discussion here: https://github.com/Mudlet/Mudlet/issues/737

This issue needs to be closed and there is no appropriate status, so will set it to "Opinion" just for migration purposes.

Changed in mudlet:
status: New → Opinion
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.