[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] a memory issue; mildly scaring to me

From: Jörg F . Wittenberger
Subject: Re: [Chicken-users] a memory issue; mildly scaring to me
Date: 25 Sep 2011 12:36:23 +0200

I'm still kinda lost.

Is there any documentation I could read to understand a little more of irregex code? The source says it should run on any Scheme; just not how. ;-)

On repeated examination my problem really looks as if it was an initialisation issue.

Just the odds have changed.  While it used to be mostly working, it's
working sometimes only now.  (Whereby mysteriously it's already somewhat
better today.  Same machine, same executable.)

That is, the actual prog is working as expected. Same way as on the other Scheme. No indication of errors, which could be relevant in the case at hand.

The strange consumption looks like this:  After a normal startup the prog
will run into about 70M or 130M virtual memory within about 3-5 seconds.
Only heavy load will make it expand beyond. Up to 2% CPU usage on my laptop.

The rarest case: after running that way for possibly really long time,
it might suddenly eat memory.

The case which recently appears at about 50% of starts: it expands within
1 second to at least 130 or more likely 240M.  Within the next seconds
it will eat 2-3G.  Thereby it will run on the same 2% CPU and work normally.
That is until the whole machine dies from swap workload.

On Sep 24 2011, Peter Bex wrote:

On Sat, Sep 24, 2011 at 06:08:13PM +0200, Jörg F. Wittenberger wrote:

I tried to change the procedure and instead of those 3 lines
I left a "return 1;" there.  This seems at least to work well
for some simple checks in csi.  But my app will now: a) run
without valgrinds complaint b) into an endless loop.

Taking into account that while compiling the DEBUGBUILD I ignored
a ton of warnings about type issues in irregex.scm, I'm kinda
alarmed that those calls to the questionable equal? originated from

Please try the current master first; it contains some bugfixes to
the types database, which make those irregex errors go away
(changeset 0fbbba9d5fc0dcce7b2364beaf3396d501967d0e).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]