2GB limit

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/9/2010 12:24 AM, Maritza Mendez wrote:
> I think I have a solid way to reproduce the VM issue, without resorting
> to ulimit.  (I'm concerned that ulimit may cause a non-problem to become
> a problem and so mask the actual problem.) 
> 
> Can someone confirm whether the trace attached is a definitive signature
> of the VM limit recently known as the 2GB limit?  I want to make sure
> I'm looking at the right problem!
> 
> Thanks!
> ~M
> 
> 

84.753  Adding the key (<bzrlib.btree_index.BTreeGraphIndex object at
0x02F73030>, 110895463, 93519167) to an LRUSizeCache failed. value
418921803 is too big to fit in a the cache with size 41943040 52428800

^- this looks like you are dealing with some very large content objects
(419MB for a single blob.)


...

  File "bzrlib\groupcompress.pyo", line 538, in _prepare_for_extract
  File "bzrlib\groupcompress.pyo", line 151, in _ensure_content
MemoryError

And this does look like it is failing during the zlib.decompress stage.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkywcmYACgkQJdeBCYSNAAMwwwCg2bWv9WSBju80HG5Z+K4g2nwR
BeEAoIAsexMDPH1h0kV81UzGTMzYe5zl
=CyUE
-----END PGP SIGNATURE-----