** Summary changed: - 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 changed: - Temporary timers 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). + 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. -- 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 _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
