RE: Big memory use after update

Hi,

If you can't recreate the memory leak problem by redoing those steps, when
the repository is in it's current state, then perhaps the problem cna be
recreated when you dump and reload up to that point, and then redo those
steps.

Looking at what you did, I don't think that reloading the repository would
trigger the problem.

regards,

--Tim

-----Original Message-----
From: Juanma Barranquero [mailto:jmbarranquero@laley.wke.es]
Sent: maandag 1 december 2003 12:54
To: Leeuw van der, Tim
Cc: users@subversion.tigris.org
Subject: Re: Big memory use after update

On Mon, 1 Dec 2003 04:57:42 -0600
"Leeuw van der, Tim" <tim.leeuwvander@nl.unisys.com> wrote:

> It happened on a commit, didn't it?

I did

  svn delete xxx
  svn delete yyy
  svn commit
  # Uh? Ahhhh, they're modified!
  svn revert
  svn status
  # What the h...??

more or less, so I'm not entirely sure whether it happened on the commit.

> So perhaps a dump/reload of that entire
> repository might trigger it on re-committing that revision?

Worth a try, if it is posible to do that.

                                                                Juanma

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 1 13:34:54 2003