[Bug 5486] New: Mercurial+evolve sometimes segfaults on pull

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=5486

            Bug ID: 5486
           Summary: Mercurial+evolve sometimes segfaults on pull
           Product: Mercurial
           Version: 4.1
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: av6 at dwimlabs.net
                CC: mercurial-devel at selenic.com,
                    pierre-yves.david at ens-lyon.org

I have a box that mirrors some repos, including Mercurial's main, once a day by
cron and occasionally, very rarely, hg pull segfaults on that repo. It's the
only repo that uses evolve and the only that has ever failed a pull. hg version
is 4.1 (installed from the ppa), evolve summary is:

parent: 1803:54120614e9e5 
 Update  tag 5.6.0 for changeset e7b6e9c4a5d4
branch: stable
bookmarks: @
commit: (clean)
update: (current)

The very rare segfaults have been happening before, but I used to have hg pull
--quiet in the cron job to not get too much mail. Here is a recent segfault
with `hg pull --verbose`:

pulling from https://www.mercurial-scm.org/repo/hg/
searching for changes
all local heads known remotely
sampling from both directions
sampling from both directions
adding changesets
adding manifests
adding file changes
added 23 changesets with 41 changes to 10 files
Segmentation fault

Now the repo has an abandoned transaction.

For comparison, here's the output from a day before, when it worked fine:

pulling from https://www.mercurial-scm.org/repo/hg/
searching for changes
all local heads known remotely
sampling from both directions
sampling from both directions
adding changesets
adding manifests
adding file changes
added 27 changesets with 54 changes to 32 files
111 new obsolescence markers
updating bookmark @
(run 'hg update' to get a working copy)

-- 
You are receiving this mail because:
You are on the CC list for the bug.