Skip to content

gh-151065: Copy fix for memory leak from mimalloc upstream#151066

Merged
ZeroIntensity merged 2 commits into
python:mainfrom
ZeroIntensity:mimalloc-leak
Jun 11, 2026
Merged

gh-151065: Copy fix for memory leak from mimalloc upstream#151066
ZeroIntensity merged 2 commits into
python:mainfrom
ZeroIntensity:mimalloc-leak

Conversation

@ZeroIntensity

@ZeroIntensity ZeroIntensity commented Jun 8, 2026

Copy link
Copy Markdown
Member

Applies microsoft/mimalloc@d7a72c4 to our copy of mimalloc.

@ZeroIntensity ZeroIntensity added the 🔨 test-with-refleak-buildbots Test PR w/ refleak buildbots; report in status section label Jun 8, 2026
@bedevere-bot

Copy link
Copy Markdown

🤖 New build scheduled with the buildbot fleet by @ZeroIntensity for commit d91dd5f 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F151066%2Fmerge

If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again.

@bedevere-bot bedevere-bot removed the 🔨 test-with-refleak-buildbots Test PR w/ refleak buildbots; report in status section label Jun 8, 2026
@ZeroIntensity ZeroIntensity marked this pull request as ready for review June 8, 2026 12:15
@ZeroIntensity ZeroIntensity requested a review from DinoV June 8, 2026 12:15
@ZeroIntensity ZeroIntensity added needs backport to 3.13 bugs and security fixes needs backport to 3.14 bugs and security fixes needs backport to 3.15 pre-release feature fixes, bugs and security fixes labels Jun 11, 2026
@ZeroIntensity ZeroIntensity merged commit 80f9467 into python:main Jun 11, 2026
87 checks passed
@ZeroIntensity ZeroIntensity deleted the mimalloc-leak branch June 11, 2026 22:11
@miss-islington-app

Copy link
Copy Markdown

Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15.
🐍🍒⛏🤖

@bedevere-app

bedevere-app Bot commented Jun 11, 2026

Copy link
Copy Markdown

GH-151383 is a backport of this pull request to the 3.15 branch.

@bedevere-app bedevere-app Bot removed the needs backport to 3.15 pre-release feature fixes, bugs and security fixes label Jun 11, 2026
@bedevere-app

bedevere-app Bot commented Jun 11, 2026

Copy link
Copy Markdown

GH-151384 is a backport of this pull request to the 3.14 branch.

@bedevere-app bedevere-app Bot removed the needs backport to 3.14 bugs and security fixes label Jun 11, 2026
@bedevere-app

bedevere-app Bot commented Jun 11, 2026

Copy link
Copy Markdown

GH-151385 is a backport of this pull request to the 3.13 branch.

@bedevere-app bedevere-app Bot removed the needs backport to 3.13 bugs and security fixes label Jun 11, 2026
ZeroIntensity added a commit that referenced this pull request Jun 11, 2026
…-151066) (GH-151384)

Applies microsoft/mimalloc@d7a72c4 to our copy of mimalloc.
(cherry picked from commit 80f9467)

Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
ZeroIntensity added a commit that referenced this pull request Jun 11, 2026
…-151066) (GH-151383)

Applies microsoft/mimalloc@d7a72c4 to our copy of mimalloc.
(cherry picked from commit 80f9467)

Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
ZeroIntensity added a commit that referenced this pull request Jun 12, 2026
…-151066) (GH-151385)

Applies microsoft/mimalloc@d7a72c4 to our copy of mimalloc.
(cherry picked from commit 80f9467)

Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
@bedevere-bot

Copy link
Copy Markdown

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot aarch64 Fedora Stable Clang 3.13 (tier-2) has failed when building commit 8754abc.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1456/builds/1121) and take a look at the build logs.
  4. Check if the failure is related to this commit (8754abc) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1456/builds/1121

Summary of the results of the build (if available):

Click to see traceback logs
Note: switching to '8754abc358aff62feb37dd5d30f16eec06d9bbaa'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8754abc358aff [3.13] gh-151065: Copy fix for memory leak from mimalloc upstream (GH-151066) (GH-151385)
Switched to and reset branch '3.13'

ar: unable to copy file 'libpython3.13d.a'; reason: No space left on device
make: *** [Makefile:1061: libpython3.13d.a] Error 1

@bedevere-bot

Copy link
Copy Markdown

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot aarch64 Fedora Stable Clang Installed 3.13 (tier-2) has failed when building commit 8754abc.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1387/builds/1121) and take a look at the build logs.
  4. Check if the failure is related to this commit (8754abc) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1387/builds/1121

Summary of the results of the build (if available):

Click to see traceback logs
Note: switching to '8754abc358aff62feb37dd5d30f16eec06d9bbaa'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8754abc358aff [3.13] gh-151065: Copy fix for memory leak from mimalloc upstream (GH-151066) (GH-151385)
Switched to and reset branch '3.13'

/usr/bin/ld: final link failed: No space left on device
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Makefile:1690: Programs/_freeze_module] Error 1

chmod: cannot access 'target/': No such file or directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants