bzr mv --auto crash: out of memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Unassigned |
Bug Description
I have moved 50 files and renamed a few of them in the process.
Running the command 'bzr mv --auto' or simulated versions results in the following error message:
bzr: out of memory
Use -Dmem_dump to dump memory to a file.
The .bzr.log file shows:
0.047 bazaar version: 2.4b5
0.047 bzr arguments: [u'mv', u'--auto', u'--dry-run']
0.078 looking for plugins in C:/Users/
0.078 looking for plugins in C:/Program Files (x86)/Bazaar/
0.109 encoding stdout as sys.stdout encoding 'cp850'
0.140 opening working tree 'C:/src/
1.201 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
1.201 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\
MemoryError
1.217 return code 3
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |
I'm not sure what a fix for this would be. mv --auto reads all the unknown files into memory and computes some line-wise statistics about what files would be similar.
Can you give a bit more information about the size of the files in question, etc.?
The best I can think of would be to write out summary information into a file rather than holding it in memory for the whole time.