Corinna Vinschen writes:
That's an awful lot of memory, and it it could easily break later mmap's
or thread stack reservations on 32 bit. Given that the default heap is
384 Megs already, I would prefer if we reserve subsequent heap memory in
chunks of 1 or 2 Megs only, to lower the pressure
Achim Gratz Stromeko at nexgo.de writes:
Load xz under GDB, break
on cygwin_exit, run it, and when it hits the breakpoint, observer the
memory layout, either in GDB, or by cat'ing /proc/≤xz's pid/maps.
OK, if it is still reproducible tomorrow I'll have a look.
I'm not sure I'm looking at
On Aug 30 09:26, Achim Gratz wrote:
Achim Gratz Stromeko at nexgo.de writes:
Load xz under GDB, break
on cygwin_exit, run it, and when it hits the breakpoint, observer the
memory layout, either in GDB, or by cat'ing /proc/≤xz's pid/maps.
OK, if it is still reproducible tomorrow I'll
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Yes, looks normal and expected from what you observed. mmap commits
memory top-down and that was apparently the first free slot big enough
to fullfil the request. The default heap size is 384 Megs and then
there's apparently not enough
On Aug 30 12:58, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Yes, looks normal and expected from what you observed. mmap commits
memory top-down and that was apparently the first free slot big enough
to fullfil the request. The default heap size is 384 Megs
On Aug 30 19:46, Corinna Vinschen wrote:
On Aug 30 12:58, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Yes, looks normal and expected from what you observed. mmap commits
memory top-down and that was apparently the first free slot big enough
to fullfil the
On Aug 30 17:03, Christopher Faylor wrote:
On Fri, Aug 30, 2013 at 09:00:48PM +0200, Corinna Vinschen wrote:
On Aug 30 19:46, Corinna Vinschen wrote:
On Aug 30 12:58, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Yes, looks normal and expected from what you
On Fri, Aug 30, 2013 at 09:00:48PM +0200, Corinna Vinschen wrote:
On Aug 30 19:46, Corinna Vinschen wrote:
On Aug 30 12:58, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Yes, looks normal and expected from what you observed. mmap commits
memory top-down and
David Stacey drstacey at tiscali.co.uk writes:
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I tried:
$ echo Hello World compress_me.txt
$ xz -9 compress_me.txt
xz: compress_me.txt: Cannot allocate
Achim Gratz Stromeko at NexGo.DE writes:
With the initial heap size set to 1MB, the same allocations for mmap work
just fine. The mmap length used by xz is the same for files of all sizes.
The large mmap is for the scratchpad memory of xz, which can be limited via
the -M option. Currently it
On Aug 29 14:34, Achim Gratz wrote:
Achim Gratz Stromeko at NexGo.DE writes:
With the initial heap size set to 1MB, the same allocations for mmap work
just fine. The mmap length used by xz is the same for files of all sizes.
The large mmap is for the scratchpad memory of xz, which can be
On 8/29/2013 11:11 AM, Corinna Vinschen wrote:
On Aug 29 14:34, Achim Gratz wrote:
Achim Gratz Stromeko at NexGo.DE writes:
With the initial heap size set to 1MB, the same allocations for mmap work
just fine. The mmap length used by xz is the same for files of all sizes.
The large mmap is
On Aug 29 11:32, Charles Wilson wrote:
On 8/29/2013 11:11 AM, Corinna Vinschen wrote:
On Aug 29 14:34, Achim Gratz wrote:
Achim Gratz Stromeko at NexGo.DE writes:
With the initial heap size set to 1MB, the same allocations for mmap work
just fine. The mmap length used by xz is the same for
On 8/29/2013 12:00 PM, Corinna Vinschen wrote:
On Aug 29 11:32, Charles Wilson wrote:
So...this is NOTABUG, right?
Right. But is a bit lame that it just fails. Does it have to use
this big buffer or would it also work with a smaller buffer, if there's
no memory chunk big enough?
From what
Corinna Vinschen writes:
I'm not exactly surprised. You're on a 32 bit machine, so you only have
2 Gigs VM. Probably some DLLs are in the way.
I know, also it might be true I've hit a less fortunate meory layout
than usual this time. However, I know there's plenty of unused memory
before
Charles Wilson writes:
Right. But is a bit lame that it just fails. Does it have to use
this big buffer or would it also work with a smaller buffer, if there's
no memory chunk big enough?
From what I understand, it will /not/ be able to perform the kinds of
tasks that -9 specifies. E.g.
On 15/11/12 06:30, JonY wrote:
On 11/15/2012 13:37, Peter Rosin wrote:
On 2012-11-15 05:40, marco atzeri wrote:
On 11/14/2012 11:09 PM, David Stacey wrote:
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I tried:
$ echo Hello World compress_me.txt
$ xz -9 compress_me.txt
xz: compress_me.txt: Cannot allocate memory
$ xz --version
xz (XZ Utils) 5.0.2
liblzma
On 11/14/2012 11:09 PM, David Stacey wrote:
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I tried:
$ echo Hello World compress_me.txt
$ xz -9 compress_me.txt
xz: compress_me.txt: Cannot allocate memory
$
On 2012-11-15 05:40, marco atzeri wrote:
On 11/14/2012 11:09 PM, David Stacey wrote:
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I tried:
$ echo Hello World compress_me.txt
$ xz -9 compress_me.txt
xz:
On 11/15/2012 13:37, Peter Rosin wrote:
On 2012-11-15 05:40, marco atzeri wrote:
On 11/14/2012 11:09 PM, David Stacey wrote:
I am trying to use 'xz -9' to compress a file, but the programme exits
with the error message 'Cannot allocate memory'. Here's what I tried:
$ echo Hello World
21 matches
Mail list logo
