bug report

[Andrew Voznytsa]

John Arbash Meinel wrote:
> Andrew Voznytsa wrote:
>> John Arbash Meinel wrote:
>>> Andrew Voznytsa wrote:
>> [...]
>>>> It seems that bzr failed during committing media/Test002.mpg which is
>>>> about 240 Mb (media/Test001.mpg was about 143 Mb).
>>>>
>>>> PC spec attached.
>>>>
>>>> bzr worked with shared repository over sftp (sftp server is localhost).
>>> Thanks for the report. Do you know how much memory was in use when it
>>> failed?
>> bzr ate around 680 Mb and crashed after some time.
>>
>> I set paging file size to 2 Gb but nothing changed.
> 
> Well, Windows has a soft limit around 1.2Gb because of how it allocates
> memory (depends on the size of each allocation and how fragmented memory
> is, etc). It has a hard limit of 2GB per process unless you do a lot of
> hacking. (You have to boot with the /3GB flag, as well as set the "large
> address aware" bit in the executable).
> 
> You don't seem to be terribly close to that amount, but all it needs is
> a single allocation that goes above to cause it to fail.
> 
> 

OK, in light of post-1.0 support of large files I'd play with /3GB and 
"large address aware" flags.

/3GB is simple; "large address aware" on Python-generated executable is 
a bit problematic for me (I'm not familiar with Python). Could you give 
me any idea how to rebuild 0.14 with this option? Or do you think PE 
header modification would be enough to allow bzr use 3GB space?

[...]

Thanks for your help,
Best regards,
Andrew Voznytsa