bzr update crashes on large update (Windows warned of low virtual memory)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
I have been using bzr to version control an installer package. The installer package contains copies of the source binaries and is pretty large. Up until now everything has been OK (13 revisions). I committed the changes on one machine successfully, but when I went to update another machine (which is a virtual machine running XP SP3 with 1GB of memory) the bzr update failed and produced the following stack trace.
Both the central server (Ubuntu Linux) and the clients (Windows XP SP3) run bzr version 1.10.
We use BZR+SSH as the transport together with putty/pageant for the key handling.
C:\nms\
bound_location = bzr+ssh:
bound = True
Any ideas?
Memory leak?
Here's the stack trace.
C:\nms\
Connected (version 2.0, client OpenSSH_4.6p1)
Authentication (publickey) successful!
Secsh channel 1 opened.
Unknown exception:
Traceback (most recent call last):
File "paramiko\
File "paramiko\
File "paramiko\
MemoryError
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\pack.pyo", line 272, in _iter_records
File "bzrlib\pack.pyo", line 277, in _iter_record_
File "bzrlib\pack.pyo", line 218, in reader_func
File "bzrlib\pack.pyo", line 177, in read
File "bzrlib\pack.pyo", line 172, in _next
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "paramiko\
MemoryError
bzr 1.10 on python 2.5.2 (win32)
arguments: ['bzr', 'update']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
bzrtools C:\Program Files\Bazaar\
launchpad C:\Program Files\Bazaar\
qbzr C:\Program Files\Bazaar\
svn C:\Program Files\Bazaar\
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
C:\nms\
C:\nms\
Bazaar (bzr) 1.10
Python interpreter: C:\Program Files\Bazaar\
Python standard library: C:\Program Files\Bazaar\
bzrlib: C:\Program Files\Bazaar\
Bazaar configuration: C:\Documents and Settings\
Bazaar log file: C:\Documents and Settings\
Copyright 2005, 2006, 2007, 2008 Canonical Ltd.
http://
bzr comes with ABSOLUTELY NO WARRANTY. bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.
Found a workaround myself. Just noticed that the XP client in VMWare did not have a page file set (it is disabled by default).
So I added a 512MB page file and retried the command. This time it completed successfully.
Just for the reference of others: you set the page file in My Computer/view system information/system properties/ advanced/ performance settings/ advanced/ virtual memory/ change/ custom size
Obviously having a page file on virtual drive is probably not the most efficient solution, but it worked.
I guess I'd still be interested to check why this operation took so much memory, although obviously it is a low priority now that the fire is nearly out. It may yet bite me one day: e.g. if the page file gets bigger.