Re: Cygwin and lz/lza running out of memory?

2013-09-23 Thread Larry Hall (Cygwin)
On 9/23/2013 2:28 AM, Matt D. wrote: On 9/22/2013 10:25 PM, Larry Hall (Cygwin) wrote: On 9/22/2013 5:30 PM, Matt D. wrote: Depending on the options I choose, I keep running into lz/lzma reporting: "ERROR: Can't allocate required memory!". This can occur before or during compression. The lz/lz

Re: Cygwin and lz/lza running out of memory?

2013-09-22 Thread Matt D.
The link sounded promising but no matter how high I set it (tried up to 8192), I get the same error, even when bringing down the compression ratio a bit. I attempted to increase the cygwin heap on both /usr/lib/p7zip/7z.exe and 7za.exe. Matt D. On 9/22/2013 10:25 PM, Larry Hall (Cygwin) wr

Re: Cygwin and lz/lza running out of memory?

2013-09-22 Thread Larry Hall (Cygwin)
On 9/22/2013 5:30 PM, Matt D. wrote: Depending on the options I choose, I keep running into lz/lzma reporting: "ERROR: Can't allocate required memory!". This can occur before or during compression. The lz/lza process tends to stop after gaining about 400MB on the process; then it exits with this

Cygwin and lz/lza running out of memory?

2013-09-22 Thread Matt D.
Depending on the options I choose, I keep running into lz/lzma reporting: "ERROR: Can't allocate required memory!". This can occur before or during compression. The lz/lza process tends to stop after gaining about 400MB on the process; then it exits with this error. The problem does not appear

Re: "du -b --files0-from=-" running out of memory

2008-11-25 Thread Jim Meyering
Pádraig Brady <[EMAIL PROTECTED]> wrote: >>> I notice that argv_iter does a malloc() + memcpy() per entry. >>> Since the sources are already NUL terminated strings >>> perhaps it could just return a pointer to a getdelim >>> realloc'd buffer which was referenced in the argv_iterator struct. >> >> T

Re: "du -b --files0-from=-" running out of memory

2008-11-25 Thread Pádraig Brady
Jim Meyering wrote: > Pádraig Brady <[EMAIL PROTECTED]> wrote: >> Jim Meyering wrote: >>> Subject: [PATCH 1/2] argv-iter: new module >>> >>> * gl/lib/argv-iter.h: New file. >>> * gl/lib/argv-iter.c: New file. >>> * gl/modules/argv-iter: New file. >> Very useful module! >> >> I see that --files0-fro

Re: "du -b --files0-from=-" running out of memory

2008-11-25 Thread Jim Meyering
Pádraig Brady <[EMAIL PROTECTED]> wrote: > Jim Meyering wrote: >> Subject: [PATCH 1/2] argv-iter: new module >> >> * gl/lib/argv-iter.h: New file. >> * gl/lib/argv-iter.c: New file. >> * gl/modules/argv-iter: New file. > > Very useful module! > > I see that --files0-from was added to `du` in Mar 20

Re: "du -b --files0-from=-" running out of memory

2008-11-25 Thread Pádraig Brady
Jim Meyering wrote: > Subject: [PATCH 1/2] argv-iter: new module > > * gl/lib/argv-iter.h: New file. > * gl/lib/argv-iter.c: New file. > * gl/modules/argv-iter: New file. Very useful module! I see that --files0-from was added to `du` in Mar 2004, so it's a nice solution to this 4 year old issue.

Re: "du -b --files0-from=-" running out of memory

2008-11-25 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote: > Eric Blake <[EMAIL PROTECTED]> wrote: >> According to Barry Kelly on 11/23/2008 6:24 AM: >>> I have a problem with du running out of memory. >>> >>> I'm feeding it a list of null-separated file names

Re: "du -b --files0-from=-" running out of memory

2008-11-24 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: > [adding the upstream coreutils list] > According to Barry Kelly on 11/23/2008 6:24 AM: >> I have a problem with du running out of memory. >> >> I'm feeding it a list of null-separated file names via standard input, &

Re: "du -b --files0-from=-" running out of memory

2008-11-23 Thread Barry Kelly
Eric Blake wrote: > [adding the upstream coreutils list] > > According to Barry Kelly on 11/23/2008 6:24 AM: > > I have a problem with du running out of memory. > > > > I'm feeding it a list of null-separated file names via standard input, > > to a command-

Re: "du -b --files0-from=-" running out of memory

2008-11-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding the upstream coreutils list] According to Barry Kelly on 11/23/2008 6:24 AM: > I have a problem with du running out of memory. > > I'm feeding it a list of null-separated file names via standard input, > to a command-lin

"du -b --files0-from=-" running out of memory

2008-11-23 Thread Barry Kelly
I have a problem with du running out of memory. I'm feeding it a list of null-separated file names via standard input, to a command-line that looks like: du -b --files0-from=- The problem is that when du is run in this way, it leaks memory like a sieve. I feed it about 4.7 million path

Re: running out of memory

2003-11-12 Thread Arash Partow
Hi Armin, This is a known problem with the cygwin layer, currently efforts are underway to exactly define where the problem resides, however it seems when "processes" are threaded and sockets are used in the process, in some instances when the socket is closed the cygwin layer doesn't pass the clo

running out of memory

2003-11-11 Thread Armin Behrendt
Hi to all, I am relatively new to this newsgroup and I am not sure, whether my question annoys you. So please don't stab at me. I did some research on this problem, though. So far unsuccessful. I am running cygwin ( l.5.5 ) on a Win 2k ( 1,8 Ghz; 512 MB Ram) machine with rsync as a service. Each n