From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Itemize without page break
Date: Thu, 22 Mar 2012 17:38:48 +0100 [thread overview]
Message-ID: <CAG5iGsC1iuFxsLaAdOr9p=AU1PRAbNPkCXRU3Bz2u__RM2MA0w@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsBGbnmiat1q+pL=YkaRPJ+Ss+WJwm7uv-4PObBtTaTkfA@mail.gmail.com>
On Thu, Mar 22, 2012 at 1:05 PM, luigi scarso <luigi.scarso@gmail.com> wrote:
> On Thu, Mar 22, 2012 at 3:01 AM, Kip Warner <kip@thevertigo.com> wrote:
>
>>What's probably happening is eventually the system runs out of memory,
>>the swap gets depleted as well, and as a last act of desperation, the
>>kernel finally denies an allocation request to luatex which is pretty
>>rare. The latter probably then dereferences the null pointer and then it
>>blows.
> Yes, can be, but LuaTex has it's memory manager that should manage
> this situation
> just to avoid segmentation faults. I will see if I'm able to setup a vm .
On a qemu vm Suse 11.3
Linux linux 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200
x86_64 x86_64 x86_64 GNU/Linux
at runlevel 3
after 7minuts I have
Runaway argument?
{before=\startlinecorrection ,after=\stoplinecorrection
}]{\dodoubleemptyYESone \ETC.
! TeX capacity exceeded, sorry [token memory size=226427358].
The vm was slow but usable, the max load factor was 2.3 . No
segmentation fault.
--
luigi
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-22 16:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 1:47 Kip Warner
2012-03-17 9:21 ` luigi scarso
2012-03-17 10:21 ` Wolfgang Schuster
2012-03-18 23:25 ` Kip Warner
2012-03-18 23:29 ` Kip Warner
2012-03-19 8:17 ` Wolfgang Schuster
2012-03-20 1:04 ` Kip Warner
2012-03-20 5:22 ` Wolfgang Schuster
2012-03-20 5:31 ` Kip Warner
2012-03-20 5:46 ` Wolfgang Schuster
2012-03-20 5:49 ` Kip Warner
2012-03-20 7:21 ` [luatex] " Patrick Gundlach
2012-03-20 15:02 ` Khaled Hosny
2012-03-20 8:17 ` Hans Hagen
2012-03-20 10:05 ` luigi scarso
2012-03-20 18:50 ` Kip Warner
2012-03-20 14:57 ` [luatex] " Khaled Hosny
2012-03-20 18:59 ` Kip Warner
2012-03-20 19:26 ` Hans Hagen
2012-03-20 19:59 ` Kip Warner
2012-03-20 20:39 ` luigi scarso
2012-03-20 21:24 ` Kip Warner
2012-03-20 21:41 ` luigi scarso
2012-03-22 1:50 ` Kip Warner
2012-03-20 20:44 ` Hans Hagen
2012-03-20 21:26 ` Kip Warner
2012-03-20 22:18 ` Kip Warner
2012-03-20 22:22 ` Aditya Mahajan
2012-03-22 2:01 ` Kip Warner
2012-03-22 10:38 ` Mojca Miklavec
2012-03-22 10:48 ` Hans Hagen
2012-03-22 10:48 ` Hans Hagen
2012-03-22 11:21 ` Philipp Gesang
2012-03-22 11:58 ` Philipp Gesang
2012-03-22 22:47 ` Kip Warner
2012-03-22 22:46 ` Kip Warner
2012-03-22 22:40 ` Kip Warner
2012-03-22 12:05 ` luigi scarso
2012-03-22 16:38 ` luigi scarso [this message]
2012-03-19 21:49 ` Hans Hagen
2012-03-20 0:43 ` Kip Warner
2012-03-20 8:11 ` Hans Hagen
2012-03-18 23:33 ` luigi scarso
2012-03-19 21:50 ` Hans Hagen
2012-03-20 0:41 ` Kip Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG5iGsC1iuFxsLaAdOr9p=AU1PRAbNPkCXRU3Bz2u__RM2MA0w@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).