[issue3253] hg log --date uses all available RAM when TO date range includes a Merge CSET on the same date as one of the end points

[Todd Morgan]

New submission from Todd Morgan <toddlmorgan at gmail.com>:

When I try to run a hg log date command like this 

hg log --date "2011-12-10 17:27:11 to 2012-02-06 17:27:11"

The log processes as normal until it gets to a Merge entry on this date
2011-12-10

At this point the hg process then proceeds to consume all the available RAM
on the system and needs to be killed.

I am able to hg log and view the appropriate entries with this command

hg log -v --limit 400

The relevant entries are detailed below (user details removed)

changeset:   11382:fe5fbaab1893
branch:      branch15
parent:      11381:ee1f3ef838b9
parent:      11368:c66124c260d8
date:        Mon Dec 12 10:32:53 2011 +1100
summary:     Merge


changeset:   11381:ee1f3ef838b9
branch:      branch15
parent:      11378:ab925627a790
date:        Fri Dec 09 11:32:53 2011 +1100
files:       configuration/pom.xml
description:
setup new style config for dev2 environment


changeset:   11368:c66124c260d8
branch:      branch15
date:        Fri Dec 09 18:03:28 2011 +1100
files:       cgu_base/src/au/com/cgu/Util.java
description:
removed unused code


Is it possible that the merge CSET causes the date range to be exceeded (as
the parents are from the 9th Dec) and this causes problems for the processing.

I discovered this as I am attempting to write a log parser to generate
release notes using the commandserver interface



I am located in Australia (GMT +10)

My platform  is:
Mercurial Distributed SCM (version 2.1)
Windows 7 SP1
Core i7 2600
8GB RAM
120 GB SSD

The repository is served from a Linux box running
Mercurial Distributed SCM (version 1.4.3)

----------
messages: 18988
nosy: toddlmorgan
priority: bug
status: unread
title: hg log --date uses all available RAM when TO date range includes a Merge CSET on the same date as one of the end points

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue3253>
____________________________________________________