Re: Tcl under conditions of high memory usage.
- From: "Larry W. Virden" <lvirden@xxxxxxxxx>
- Date: Thu, 29 Nov 2007 08:50:00 -0800 (PST)
On Nov 29, 3:16 am, "neuronst...@xxxxxxxxx" <neuronst...@xxxxxxxxx>
wrote:
is it normal for the app to just crash?
It is normal for a tcl application that uses up all of memory to
abort.
It is relatively simple to create examples of this. The error I see
when my sample runs out of memory is
"Not enough memory to allocate list". But of course, that message will
vary, depending on what request is being made when malloc returns an
error.
It would be nice if a stack were generated before the abort.
What are some alternatives that the language might take in this case?
Remember, once memory is exhasuted, one can't even guarantee a printed
output - since the attempt to puts the message out _could_ potentially
encounter the exhausted resource in the process of generating the
error. And you can't depend on having stdin, stdout, and stderr
attached to anything useful, though I suppose that particular actions
could take place if those were attached to something useful. Again
though, one has a process in an unstable situation at this point, so
useful actions might be at a minimum.
.
- Follow-Ups:
- Re: Tcl under conditions of high memory usage.
- From: billposer
- Re: Tcl under conditions of high memory usage.
- References:
- Tcl under conditions of high memory usage.
- From: neuronstorm@xxxxxxxxx
- Tcl under conditions of high memory usage.
- Prev by Date: Re: Tcl under conditions of high memory usage.
- Next by Date: Re: Using a tcl interpreter inside a DLL?
- Previous by thread: Re: Tcl under conditions of high memory usage.
- Next by thread: Re: Tcl under conditions of high memory usage.
- Index(es):
Relevant Pages
|