From: Derrick Stolee <stolee@gmail.com>
To: Elijah Newren <newren@gmail.com>, git@vger.kernel.org
Cc: Derrick Stolee <dstolee@microsoft.com>, Jeff King <peff@peff.net>,
Jonathan Nieder <jrnieder@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>,
Taylor Blau <me@ttaylorr.com>,
gitster@pobox.com
Subject: Re: [PATCH v4 1/3] merge-ort: fix massive leak
Date: Sun, 24 Jan 2021 14:11:54 -0500 [thread overview]
Message-ID: <7e1c184f-4745-530d-8aca-879319786845@gmail.com> (raw)
In-Reply-To: <20210124060112.1258291-2-newren@gmail.com>
On 1/24/2021 1:01 AM, Elijah Newren wrote:
> When a series of merges was performed (such as for a rebase or series of
> cherry-picks), only the data structures allocated by the final merge
> operation were being freed. The problem was that while picking out
> pieces of merge-ort to upstream, I previously misread a certain section
> of merge_start() and assumed it was associated with a later
> optimization. Include that section now, which ensures that if there was
> a previous merge operation, that we clear out result->priv and then
> re-use it for opt->priv, and otherwise we allocate opt->priv.
>
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
> merge-ort.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/merge-ort.c b/merge-ort.c
> index 05c6b2e0dc..b5845ff6e9 100644
> --- a/merge-ort.c
> +++ b/merge-ort.c
> @@ -3227,11 +3227,28 @@ static void merge_start(struct merge_options *opt, struct merge_result *result)
> assert(opt->obuf.len == 0);
>
> assert(opt->priv == NULL);
> + if (result->priv) {
> + opt->priv = result->priv;
> + result->priv = NULL;
> + /*
> + * opt->priv non-NULL means we had results from a previous
> + * run; do a few sanity checks that user didn't mess with
> + * it in an obvious fashion.
> + */
> + assert(opt->priv->call_depth == 0);
> + assert(!opt->priv->toplevel_dir ||
> + 0 == strlen(opt->priv->toplevel_dir));
> + }
So instead of simply leaking result->priv, we re-use the
data for the next round.
>
> /* Default to histogram diff. Actually, just hardcode it...for now. */
> opt->xdl_opts = DIFF_WITH_ALG(opt, HISTOGRAM_DIFF);
>
> /* Initialization of opt->priv, our internal merge data */
> + if (opt->priv) {
> + clear_or_reinit_internal_opts(opt->priv, 1);
> + trace2_region_leave("merge", "allocate/init", opt->repo);
> + return;
> + }
> opt->priv = xcalloc(1, sizeof(*opt->priv));
and here you reset the data instead of reallocating it. OK.
-Stolee
next prev parent reply other threads:[~2021-01-24 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 20:51 [PATCH 0/1] And so it begins...merge/rename performance work Elijah Newren
2021-01-08 20:51 ` [PATCH 1/1] merge-ort: begin performance work; instrument with trace2_region_* calls Elijah Newren
2021-01-08 20:59 ` Taylor Blau
2021-01-08 21:50 ` Elijah Newren
2021-01-08 21:55 ` Taylor Blau
2021-01-09 0:52 ` Elijah Newren
2021-01-13 22:11 ` [PATCH v2 0/1] And so it begins...merge/rename performance work Elijah Newren
2021-01-13 22:11 ` [PATCH v2 1/1] merge-ort: begin performance work; instrument with trace2_region_* calls Elijah Newren
2021-01-14 19:08 ` [PATCH v2 0/1] And so it begins...merge/rename performance work Junio C Hamano
2021-01-14 20:18 ` Elijah Newren
2021-01-15 19:29 ` [PATCH v3 " Elijah Newren
2021-01-15 19:29 ` [PATCH v3 1/1] merge-ort: begin performance work; instrument with trace2_region_* calls Elijah Newren
2021-01-24 6:01 ` [PATCH v4 0/3] And so it begins...merge/rename performance work Elijah Newren
2021-01-24 6:01 ` [PATCH v4 1/3] merge-ort: fix massive leak Elijah Newren
2021-01-24 19:11 ` Derrick Stolee [this message]
2021-01-24 6:01 ` [PATCH v4 2/3] merge-ort: ignore the directory rename split conflict for now Elijah Newren
2021-01-24 6:01 ` [PATCH v4 3/3] merge-ort: begin performance work; instrument with trace2_region_* calls Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e1c184f-4745-530d-8aca-879319786845@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.