Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: treap implementation of find() doesn't return the best-fit span [1.12 backport] #31677

gopherbot opened this issue Apr 25, 2019 · 2 comments


Copy link

@gopherbot gopherbot commented Apr 25, 2019

@mknyszek requested issue #31616 to be considered for backport to the next 1.12 minor release.

@gopherbot please open a backport to 1.12. The VSS growth problem has been bad enough that it's prevented some users from being able to move to 1.12, since some of the heap metadata grows proportionally with the amount of mapped memory.

Copy link

@gopherbot gopherbot commented Apr 25, 2019

Change mentions this issue: runtime: make mTreap.find actually find the best fit

Copy link

@gopherbot gopherbot commented Apr 26, 2019

Closed by merging 438b1a5 to release-branch.go1.12.

@gopherbot gopherbot closed this Apr 26, 2019
gopherbot pushed a commit that referenced this issue Apr 26, 2019
…est fit

This change modifies the implementation of mTreap.find to find the
best-fit span with the lowest possible base address.

Fixes #31677.

Change-Id: Ib4bda0f85d7d0590326f939a243a6e4665f37d3f
Run-TryBot: Michael Knyszek <>
TryBot-Result: Gobot Gobot <>
Reviewed-by: Austin Clements <>
(cherry picked from commit 8c05d67)
Reviewed-by: Brad Fitzpatrick <>
@golang golang locked and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.