Re: [Sablevm-developer] Runaway memory usage

[Etienne M. G. <eti...@uq...>]

On Thu, Dec 12, 2002 at 05:02:24PM -0800, Archie Cobbs wrote:
> I've upgraded Soot from 1.2.3 to 1.2.4 and now I'm having a problem
> running it with SableVM (version 1.0.5).
> 
> The problem is that the sablevm process seems to eat up an infinite
> amount of memory, bringing my machine to a grinding, thrashing halt.
> 
> I've tried to limit sablevm by adding this to my ~/.sablevm file:
> 
>     property = sablevm.heap.size.increment=0
>     property = sablevm.heap.size.min=16777216
>     property = sablevm.heap.size.max=16777216
>     property = sablevm.classloader.heap.size.increment=0
>     property = sablevm.classloader.heap.size.min=16777216
>     property = sablevm.classloader.heap.size.max=16777216
>...

That was a good idea.

Now, it seems we need to know which allocation site is causing these
problems.  You might want to poke around using electric-fence (and/or
other malloc debuggers) to try identifying the leaking site.

http://metalab.unc.edu/pub/Linux/devel/lang/c/ElectricFence-2.0.5.tar.gz

On Debian: 

$ apt-get install electric-fence
$ LD_PRELOAD=libefence.so sablevm soot.Main -O --jimple Test

and 

$ man efence

Etienne

-- 
Etienne M. Gagnon                    http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/