From owner-freebsd-hackers  Tue Aug 17  1: 0:23 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from relex.relex.ru (slip.relex.ru [195.98.69.100])
	by hub.freebsd.org (Postfix) with ESMTP id 5450A1577C
	for <freebsd-hackers@freebsd.org>; Tue, 17 Aug 1999 01:00:01 -0700 (PDT)
	(envelope-from alec@relex.relex.ru)
Received: from alec.relex.ru (alec.relex.ru [195.98.69.163]) by relex.relex.ru (8.8.8/Relcom-2A) with SMTP
	 id LAA14248  for <freebsd-hackers@freebsd.org>;Tue, 17 Aug 1999 11:49:23 +0400 (MSD)
Message-ID: <01b001bee885$cca7b570$a34562c3@alec.relex.ru>
From: "Alec Kalinin" <alec@relex.ru>
To: <freebsd-hackers@freebsd.org>
Subject: Probably bug with allocation memory in FreeBSD-3.2-RELEASE
Date: Tue, 17 Aug 1999 11:54:57 +0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello!

I think, mentioned below program probably show the bug in virtual memory
subsystem in FreeBSD-3.2-RELEASE. After running this program, FreeBSD comes
into "out of swap" state, then hungs.

Why i think this is bug? Because any user can hung FreeBSD, settings in
/etc/login.conf can't help.
Note: in FreeBSD-2.2.8 there is no this problem. The 2.2.8-system
successfully kill this program.

--------------------------------------------------------------------
#include <unistd.h>
#include <stdlib.h>

#define NALLOC          1000
#define SIZEALLOC       1024*1024

void main()
{
 char *p_mem;
 int i, j;

 if (fork() != 0) return;

 for (i=0; i<NALLOC; i++) {
     p_mem = (char *)malloc(SIZEALLOC);
     for (j=0; j<SIZEALLOC; j++) {
         p_mem[j] = 0;
     }
 }

 while (1);
}
--------------------------------------------------------------------

P.S. Sorry for my English...

Good luck,
            Alec



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message