On Tue, 2012-03-20 at 22:41 +0100, luigi scarso wrote:
> > As I said earlier, I get a segmentation fault if I leave it to run, but
> > I always have to kill it before it takes down the entire operating
> > system with it (apparently this is normal). I don't get the TeX capacity
> > exceeded error m
On Tue, Mar 20, 2012 at 10:24 PM, Kip Warner wrote:
> On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
>> 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 mki
On Tue, 2012-03-20 at 21:44 +0100, Hans Hagen wrote:
> sure, but mu experience is that browsers of email clients are way more
> demanding than tex when it comes to memory usage
I've never had either take down the entire operating system. There is a
different from intended memory usage and uninten
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
> 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:
On 20-3-2012 20:59, Kip Warner wrote:
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 wil
On Tue, Mar 20, 2012 at 8:59 PM, Kip Warner wrote:
> 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
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 i
On 20-3-2012 19:59, Kip Warner wrote:
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
Older TeX engines had hard memory limit, so in case of such
"syntactical" errors the engine would consume all its allocated memory
and die (with a misleading error message), LuaTeX dynamically allocates
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
> Older TeX engines had hard memory limit, so in case of such
> "syntactical" errors the engine would consume all its allocated memory
> and die (with a misleading error message), LuaTeX dynamically allocates
> memory (for good reasons) so it w
On Tue, Mar 20, 2012 at 08:21:35AM +0100, Patrick Gundlach wrote:
>
> Am 20.03.2012 um 06:49 schrieb Kip Warner:
>
> > On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
> >> TeX has it’s problem with certain errors, accept it.
> >
> > It is not a problem with the program raising an err
On Mon, Mar 19, 2012 at 10:49:48PM -0700, Kip Warner wrote:
> On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
> > TeX has it’s problem with certain errors, accept it.
>
> It is not a problem with the program raising an error, it was how it
> went about doing it. It should not have to t
Am 20.03.2012 um 06:49 schrieb Kip Warner:
> On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
>> TeX has it’s problem with certain errors, accept it.
>
> It is not a problem with the program raising an error, it was how it
> went about doing it. It should not have to take down the ent
12 matches
Mail list logo
