summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/dat/clua
diff options
context:
space:
mode:
authorMatthew Cline <zelgadis@sourceforge.net>2009-11-13 03:12:21 -0800
committerMatthew Cline <zelgadis@sourceforge.net>2009-11-13 03:12:21 -0800
commita228636066120596757c3d395fdb802ba107063f (patch)
tree5a523f9eea0ba72f7781e3151a840ec8721dd943 /crawl-ref/source/dat/clua
parentada5301a6dd6ba6d713a7aeb566d1ef14a000eb1 (diff)
downloadcrawl-ref-a228636066120596757c3d395fdb802ba107063f.tar.gz
crawl-ref-a228636066120596757c3d395fdb802ba107063f.zip
Don't remove marker while it's being activated
Removing a marker while it's being activated leads to memory weirdness, so instead while activating all markers see if each marker has the "post_activate_remove" set, and afterwards remove those that do.
Diffstat (limited to 'crawl-ref/source/dat/clua')
-rw-r--r--crawl-ref/source/dat/clua/lm_mon_prop.lua14
1 files changed, 13 insertions, 1 deletions
diff --git a/crawl-ref/source/dat/clua/lm_mon_prop.lua b/crawl-ref/source/dat/clua/lm_mon_prop.lua
index 6bc3dd6de9..f005a4b0d9 100644
--- a/crawl-ref/source/dat/clua/lm_mon_prop.lua
+++ b/crawl-ref/source/dat/clua/lm_mon_prop.lua
@@ -38,7 +38,19 @@ function MonPropsMarker:activate(marker)
mon.set_prop(k, v)
end
- dgn.remove_marker(marker)
+ -- NOTE: do *not* call dgn.remove_marker() right now; removing a marker
+ -- while it's being activated causes memory problems. We'll be
+ -- removed after activation is done with the "post_activate_remove"
+ -- property.
+ self.want_remove = true
+end
+
+function MonPropsMarker:property(marker, pname)
+ if self.want_remove and pname == "post_activate_remove" then
+ return "true"
+ end
+
+ return ""
end
function MonPropsMarker:write(marker, th)