From owner-freebsd-questions@FreeBSD.ORG Tue Mar 1 18:08:52 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E0A816A4CE for ; Tue, 1 Mar 2005 18:08:52 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 018B043D5E for ; Tue, 1 Mar 2005 18:08:52 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j21I8jMK070377; Tue, 1 Mar 2005 12:08:45 -0600 (CST) (envelope-from dan) Date: Tue, 1 Mar 2005 12:08:45 -0600 From: Dan Nelson To: Per olof Ljungmark Message-ID: <20050301180845.GQ8778@dan.emsphone.com> References: <42246457.70200@intersonic.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42246457.70200@intersonic.se> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: "'freebsd-questions@freebsd.org'" Subject: Re: Perl out of memory [sbrk()] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 18:08:52 -0000 In the last episode (Mar 01), Per olof Ljungmark said: > I'm running imapsync that also uses p5-Mail-IMAPClient-2.2.9 to transfer > mailboxes between imap servers. > > The following error occurs when a message has an attachment of more that > approx 35MB in size: > "Out of memory during "large" request for 67112960 bytes, total sbrk() > is 487512064 bytes at /usr/local/bin/imapsync line 790." According to that output, perl was already using 464MB, and a malloc request for 64MB failed, which is reasonable since the default hard datasize limit on FreeBSD is 512MB. To raise it, put this in /boot/loader.conf and reboot: kern.maxdsiz="1024M" > Running 5.3-STABLE a week or so old > Perl 5.8.6 from ports. > > What bothers me especially is that this error will not occur when I run > the same command from a old RH Linux (7.2) box. Appriciate comments Also running perl 5.8.6, on the same mailbox? Maybe different perl versions allocate memory differently. -- Dan Nelson dnelson@allantgroup.com