On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { } while true do t[#t+1] = "just a bogus string: " .. (#t+1) end
at some point your system will run out of (virtual) memory or lua will run out of whatever its limits are
Of course. And the same could be done in C, C++, or really any language that supports dynamic memory allocation. We just hope that programs that are built from them won't do that. When TeX says ! TeX capacity exceeded, sorry [token memory size=<...>] it is its graceful way to exit from an irreversible situation. It can be caused by luatex or ConTeXt mkiv but it's *not* a segmentation fault, as you said early: Actually highly probably, since the seg fault is raised in luatex and not context. Even if context is feeding it malformed input, luatex should not ever crash. Only luatex can do a segmentation fault -- of course due a tex macro /lua function possibly called from ConTeXt. What happen for me (linux ubuntu 10lts 32bit) and Hans (windows (7
On Tue, Mar 20, 2012 at 8:59 PM, Kip Warner