* Daniel Shahaf :
> Presumably, tcpdump/wireshark of the response headers will be useful.
The problem was very subtle:
Apache delivered a P3P header (our own configuration). This broke the checkout.
Why only a certain file was affected (it worked when the file was not in the
repo) or why it worke
Presumably, tcpdump/wireshark of the response headers will be useful.
Daniel
(no time to dive deeply into this right now, sorry)
Fridtjof Busse wrote on Tue, Mar 06, 2012 at 12:44:06 +0100:
> Hi,
>
> answering my own post:
>
> * Fridtjof Busse :
> >
> > The httpd process starts consuming up to
Am 05.03.2012 09:30, schrieb Fridtjof Busse:
we're running a SVN repo (~6GB) on 1.7.3. Checking out the entire
repo in one "svn co" (both 1.6 and 1.7) session is almost
impossible. The httpd process starts consuming up to 4GB and then
dies...
Note: The repository size and the size of a checkout
Hi,
answering my own post:
* Fridtjof Busse :
>
> The httpd process starts consuming up to 4GB and then dies, killing the
> svn client process with:
> svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read chunk size:
> connection was closed by server
Setting the configuration to
SVNAllowBu
> >> It might already be fixed: I see a leak with 1.7.x@r1293812 but
r1293813
> >> appears to fix it.
> >
> > Definitely not fixed, at least for https:// externals. This is what I
> > did:
>
> I see small memory growth during checkout. I see much larger memory
> growth for a second checkout o
kmra...@rockwellcollins.com writes:
>> It might already be fixed: I see a leak with 1.7.x@r1293812 but r1293813
>> appears to fix it.
>
> Definitely not fixed, at least for https:// externals. This is what I
> did:
I see small memory growth during checkout. I see much larger memory
growth for
> > Has anyone else noticed a client memory leak when using
> > svn:externals in the 1.7.3 client?
> >
> > We have a large project with tens of thousands of externals.
> > When checked out with a 1.6 client, it uses 150MB of memory.
> > When checked out with a 1.7 client it uses >1.5GB of memory.
>
> > Has anyone else noticed a client memory leak when using
> > svn:externals in the 1.7.3 client?
> >
> > We have a large project with tens of thousands of externals.
> > When checked out with a 1.6 client, it uses 150MB of memory.
> > When checked out with a 1.7 client it uses >1.5GB of memory.
>
kmra...@rockwellcollins.com writes:
> Has anyone else noticed a client memory leak when using
> svn:externals in the 1.7.3 client?
>
> We have a large project with tens of thousands of externals.
> When checked out with a 1.6 client, it uses 150MB of memory.
> When checked out with a 1.7 client it
On Mon, Feb 27, 2012 at 10:04:59AM -0600, kmra...@rockwellcollins.com wrote:
> All,
>
> Has anyone else noticed a client memory leak when using
> svn:externals in the 1.7.3 client?
>
> We have a large project with tens of thousands of externals.
> When checked out with a 1.6 client, it uses 150MB
On 14.10.2011 13:17, Stefan Sperling wrote:
> The perl bindings don't abstract away memory pool handling.
> If you don't pass a pool argument to fs->revision_root(),
> it will use the global pool, which can never be cleared.
>
> You need to use an iteration pool in your script and clear it after
>
On Fri, Oct 14, 2011 at 12:33:08AM +0200, Max Voit wrote:
> Hi,
>
> developing an application dealing with many repositories the existence
> of paths within that repositories had to be checked.
> Using something like:
>
> my $repos = SVN::Repos::open($localpath) or die "no such repo";
> m
Does it also reproduce if you remove the revision_root() call?
What does Perl invoke when an object becomes unreferenced or falls out
of scope?
Max Voit wrote on Fri, Oct 14, 2011 at 00:33:08 +0200:
> Hi,
>
> developing an application dealing with many repositories the existence
> of paths withi
> > I have a problem, apache is eating al my memory. It seems to allocate
> the
> > memory while I checkout or commit things. But then it don't
> deallocate the
> > memory after it is finish. Instead it just allocate more and more
> until the
> > memory is filled up.
>
> Only other known issue i
On Mon, Jul 12, 2010 at 6:22 AM, Lisa Ryrholm wrote:
> I have a problem, apache is eating al my memory. It seems to allocate the
> memory while I checkout or commit things. But then it don’t deallocate the
> memory after it is finish. Instead it just allocate more and more until the
> memory is f
15 matches
Mail list logo