Would you be able to install Meliae (lp:meliae), and then when memory
consumption gets big use either SIGQUIT (Ctrl+\) or SIGBREAK
(Ctrl+Pause/Break) on Windows to get into a debugger. And then run:
from meliae import scanner
scanner.dump_all_objects('memory.dump')
And then bzip2 the result and attach it to this bug?
That would make it easier to determine where the memory is actually
being consumed.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter Bex wrote: /code.launchpad .net/~peter- bex/chamilo/ chamilo- hg-mirror /code.launchpad .net/~peter- bex/chamilo/ chamilo- classic- hg-mirror /answers. edge.launchpad. net/launchpad- 118906
> Public bug reported:
>
> While downloading the initial set of revisions, hg-bzr blows up in
> memory causing Launchpad's bzr integration to fail on importing these
> two branches:
>
> https:/
>
> and
>
> https:/
>
> I got 1.6G of memory used during the process of fetching manifests early
> on: at 500/4219
>
> See also https:/
> code/+question/
>
> ** Affects: bzr-hg
> Importance: Undecided
> Status: New
>
Would you be able to install Meliae (lp:meliae), and then when memory
consumption gets big use either SIGQUIT (Ctrl+\) or SIGBREAK
(Ctrl+Pause/Break) on Windows to get into a debugger. And then run:
from meliae import scanner dump_all_ objects( 'memory. dump')
scanner.
And then bzip2 the result and attach it to this bug?
That would make it easier to determine where the memory is actually
being consumed.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
Nx+MACgkQJdeBCY SNAAMHiACgmALF4 yx8dI3q+ o2g/NwHSO3B QGwoixf+ 4QsbXQhzUWl
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkx
CmQAn2dGrIYr+
=umdh
-----END PGP SIGNATURE-----