Comment 28 for bug 109114

I am also waiting for a resolution of this issue since a couple of
years. For me, this is still a showstopper to use bazaar. Is it not possible
to provide a workaround and to resolve this issue later correctly?

However, I can completely understand that it's not a "normal" use of a VCS
to commit files with hundreds of megabytes in size.

On Fri, Jun 25, 2010 at 11:43, Andrew Voznytsa <email address hidden>wrote:

> Yes, I did not see any noticeable movement with this issue. Time to move to
> git?
>
> On Fri, Jun 25, 2010 at 9:32 AM, Greg <email address hidden> wrote:
>
> > Is this issue still not resolved after 3 years?
> > I am trying to add and commit a 600mb data file and getting bzr out of
> > memory.
> > Running Windows 7, 64bit, 6GB RAM, bzrlib 2.1.1 from Bazaar Explorer.
> >
> > --
> > [master] bzr holds whole files in memory; raises MemoryError on large
> files
> > https://bugs.launchpad.net/bugs/109114
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
> --
> [master] bzr holds whole files in memory; raises MemoryError on large files
> https://bugs.launchpad.net/bugs/109114
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> Bazaar reads each source file completely into memory when committing, which
> means files that are comparable in size to the machine's vm can't be
> committed. This currently gives a MemoryError.
>
> We also store too many copies in memory. This is being worked on by John.
> However even when fixed we'll still be limited by size. Fixing this bug
> requires some sort of fragmentation capacity when large files are detected.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/bzr/+bug/109114/+subscribe
>