Services & Resources / Wolfram Forums / MathGroup Archive
-----

MathGroup Archive 2012

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Kernel exits (for lack of memory)

  • To: mathgroup at smc.vnet.net
  • Subject: [mg128176] Re: Kernel exits (for lack of memory)
  • From: Joseph Gwinn <joegwinn at comcast.net>
  • Date: Fri, 21 Sep 2012 04:13:44 -0400 (EDT)
  • Delivered-to: l-mathgroup@mail-archive0.wolfram.com
  • Delivered-to: l-mathgroup@wolfram.com
  • Delivered-to: mathgroup-newout@smc.vnet.net
  • Delivered-to: mathgroup-newsend@smc.vnet.net
  • References: <k2s2re$dq5$1@smc.vnet.net> <k368j5$1ud$1@smc.vnet.net> <k398vo$9p0$1@smc.vnet.net> <k3c1e1$evh$1@smc.vnet.net>

In article <k3c1e1$evh$1 at smc.vnet.net>, dgolber at aol.com wrote:

> On Tuesday, September 18, 2012 3:49:26 AM UTC-4, Joseph Gwinn wrote:
> The Out[] variables are storing all results, just in case you ask for them. 
> Set $HistoryLength to zero to turn this off. One can also Clear[] 
> intermediate variables to reduce memory footprint. Joe Gwinn
> 
> ======
> 
> The example I am posting next sets $HistoryLength=0 and still shows this 
> behavior.

OK.  Will look.


> What variables am I supposed to Clear[]????  It isn't Out, because 
> $HistoryLength is zero.  I suspect it is internal variables of FindMinimum 

I doubt that FindMinimum is keeping anything hidden between calls, but 
one can tell by sprinkling MemoryInUse[] calls through the notebook, to 
tell where the weight is gained.


> In any case, the MemoryInUse is not building up after many calls, so this 
> seems unlikley to be the cause of the kernel exit.

When the kernel exits, what does it say?

Also, what is written to the system log?

Joe Gwinn



  • Prev by Date: Re: Exact Schur Decomposition
  • Next by Date: Re: Inset BezierCurve
  • Previous by thread: Re: Kernel exits (for lack of memory)
  • Next by thread: Inset BezierCurve