Subject: Re: brk(2) failed [internal error]: malloc problem or simply not enough memory?
To: None <current-users@netbsd.org>
From: Klaus Heinz <k.heinz.jul.zwei@onlinehome.de>
List: current-users
Date: 07/22/2002 18:44:00
Manuel Bouyer wrote:
> On Sun, Jul 21, 2002 at 08:35:10PM +0200, Klaus Heinz wrote:

> >    PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COM=
MAND
> >   5008 heinz     63    0    34M   35M RUN        4:40 71.92% 71.92% cc1=
plus

> What are the process limits ? On the sun3, it's too low to compile libc, I
> have to unlimit before starting build.sh

Manuel hit the nail on the head.

  $ sysctl proc.curproc.rlimit
  ...
  proc.curproc.rlimit.datasize.soft =3D 33554432
  proc.curproc.rlimit.datasize.hard =3D 134217728
  proc.curproc.rlimit.stacksize.soft =3D 2097152
  proc.curproc.rlimit.stacksize.hard =3D 33554432
  proc.curproc.rlimit.memoryuse.soft =3D 90374144
  proc.curproc.rlimit.memoryuse.hard =3D 90374144
  proc.curproc.rlimit.memorylocked.soft =3D 30124714
  proc.curproc.rlimit.memorylocked.hard =3D 90374144
  ...

=46rom those values, datasize.soft probably limited the size of the compile=
r.

The necessary size was this:

  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
  376 heinz     61    0    38M   39M RUN        9:11 93.70% 93.70% cc1plus


The compiler should definitely handle this more gracefully, if possible
at all. Spewing out thousands of lines of

  nsDOMClassInfo.cpp: cc1plus in free(): warning: recursive call.
  cc1plus in malloc(): warning: recursive call.

is not very nice.

 =20
ciao
     Klaus