bzr traceback report : Memory problem

[Jurgen Defurne]

On Wed, 7 May 2008 22:08:05 +0200
Jurgen Defurne <jurgen.defurne at pandora.be> wrote:

> 
> 
> Begin doorgestuurd bericht:
> 
> Datum: Tue, 6 May 2008 10:01:17 +0200
> Van: "Defurne, Jurgen" <jurgen.defurne at philips.com>
> Aan: "jurgen.defurne at pandora.be" <jurgen.defurne at pandora.be>
> Onderwerp: bzr traceback report
> 
> 
> deleted space/prod/rfs/rfshetv/htv520eu/htv520eu.xml
> deleted space/prod/rfs/rfshetv/htv520eu/htv520eu_makefile
> deleted space/prod/rfs/rfshetv/htv520eu/startup
> deleted space/prod/rfs/rfshetv/htv520eu/startup_5050
> deleted space/prod/rfs/rfshetv/htv520eu/version.txt
> deleted space/prod/rfs/rfshetv/tools/opensource_info/Approval/TV520 R2 OSS Compliance (2k8) v1.5.ppt
> bzr: ERROR: exceptions.MemoryError:
> 
> Traceback (most recent call last):
>   File "bzrlib\commands.pyc", line 846, in run_bzr_catch_errors
>   File "bzrlib\commands.pyc", line 802, in run_bzr
>   File "bzrlib\commands.pyc", line 504, in run_argv_aliases
>   File "bzrlib\builtins.pyc", line 2381, in run
>   File "bzrlib\decorators.pyc", line 165, in write_locked
>   File "bzrlib\workingtree_4.pyc", line 246, in commit
>   File "bzrlib\decorators.pyc", line 165, in write_locked
>   File "bzrlib\mutabletree.pyc", line 190, in commit
>   File "bzrlib\commit.pyc", line 373, in commit
>   File "bzrlib\repository.pyc", line 139, in commit
>   File "bzrlib\repository.pyc", line 917, in commit_write_group
>   File "bzrlib\repofmt\pack_repo.pyc", line 2004, in _commit_write_group
>   File "bzrlib\repofmt\pack_repo.pyc", line 1665, in _commit_write_group
>   File "bzrlib\repofmt\pack_repo.pyc", line 1230, in autopack
>   File "bzrlib\repofmt\pack_repo.pyc", line 1244, in _execute_pack_operations
>   File "bzrlib\repofmt\pack_repo.pyc", line 589, in pack
>   File "bzrlib\repofmt\pack_repo.pyc", line 722, in _create_pack_from_packs
>   File "bzrlib\repofmt\pack_repo.pyc", line 686, in _copy_text_texts
>   File "bzrlib\repofmt\pack_repo.pyc", line 807, in _copy_nodes_graph
>   File "bzrlib\repofmt\pack_repo.pyc", line 846, in _do_copy_nodes_graph
>   File "bzrlib\pack.pyc", line 155, in add_bytes_record
>   File "bzrlib\pack.pyc", line 132, in write_func
>   File "bzrlib\repofmt\pack_repo.pyc", line 303, in _write_data
> MemoryError
> 
> bzr 1.4 on python 2.5.2 (win32)
> arguments: ['c:\\Program Files\\Bazaar\\bzr.exe', 'commit', '-m', 'Platform baseline plf_R2.7_B0818.1_1']
> encoding: 'cp1252', fsenc: 'mbcs', lang: None
> plugins:
>   launchpad            C:\Program Files\Bazaar\plugins\launchpad [unknown]
> *** Bazaar has encountered an internal error.
>     Please report a bug at https://bugs.launchpad.net/bzr/+filebug
>     including this traceback, and a description of what you
>     were doing when the error occurred.
> 
> real    26m21.198s
> user    0m0.015s
> sys     0m0.015s
> 
> Current action : committing
> - source tree size :
>   - 84964 files
>   - 21662 directories
> - commit change (adds, deletes and modifies) :
>   27928 files modified
> 
> Current size of repo : ~10 Gb, containing 9 commits
> 
> Regards,
> 
> Jurgen

Dear all,

I posted this a couple of days ago, then some further information by means of gmane, which unfortunately did not get through.

What I have here is a repository with 10 commits, of a tree of about 2 Gb in size, with 60000 files. In order to test bzr for my purposes, whenever I create a new baseline in our current VCS, I update a work area, which I then commit to bzr. This has gone well for about 9 or 10 commits, but the last baseline I try to commit gives me the previous response.

My main platform is on Windows (not my own choice). I am currently busy tarring the repository, in order to deploy it under Linux, to see what happens there. On the Windows machine, the commit stops, and Task Manager reports a peak usage of 1.6 Gb. On my Linux machine I have 2 Gb of RAM, plus 2 Gb of swap. When I was retrying the commit, I noticed larges peaks of memory usage.

What I want to do is to see first if the commit succeeds with more memory, and then try what you want me to do with the repository. Since it is rather large, I cannot provide it to you, and it contains proprietary code, which I rather do not want to leak to the Internet.

Regards,

Jurgen