[cvsnt] Memory allocation error help

Lehman, Curtis CLehman at carrieraccess.com
Wed Jun 6 00:41:35 BST 2007


I'm starting to run into the same issue on my systems. I'm thinking of
trying to delete some of the intermittent versions of the Binaries that
aren't needed any more. I haven't tried it myself, but it looks like you
can use the cvsnt admin command.

Thanks,
Curtis Lehman
 
============================================================
This transmission may contain privileged or confidential information and
attachments protected from disclosure. If you are not the intended
recipient, you are instructed not to review this transmission and are
hereby notified that any reproduction, dissemination or distribution of
this communication is strictly prohibited. If you are not the intended
recipient and/or have received this communication in error, please
notify the sender that you received this message and delete this
transmission from your system. Thank you. Carrier Access Corporation.
============================================================

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Glen Starrett
Sent: Tuesday, June 05, 2007 5:34 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Memory allocation error help

Chris Terenzi wrote:
> Hi, I have a CVSNT repository that contains a number of large-ish
binary
> files. While attempting to checkout one of my modules today (over 500
> MB) I received the dreaded "out of memory; can not reallocate
335544320
> bytes" error. We will soon be moving to a better solution for our
binary
> files, but in the meantime, what can I do to alleviate my woes. I am
> currently using build 2.5.03.2382, would upgrading to 2.5.04.2471 be
> recommended? I tried increasing my VM, but that did not work. 

Sounds like this is on a Win32 machine.  We have a patch in our 
commercial build that will be in the next 2.5.04 release (some time 
soon, I think).  You could also purchase commercial support and use our 
fix now.

Another immediate (and no cost) option would be to move to a *nix 
server, which doesn't have the Win memory issues that require this 
workaround.

Regards,


-- 
Glen Starrett
Technical Account Manager, North America
March Hare Software, LLC

http://march-hare.com/cvspro/
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt


More information about the cvsnt mailing list