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

BUG: Fix two errors related to not checking for failed allocations #25425

Merged
merged 1 commit into from
Dec 19, 2023

Conversation

seberg
Copy link
Member

@seberg seberg commented Dec 18, 2023

Tracking down issues in the 32bit debug run, it turned out to be a memory leak and the crashes were just memory errors that were not propagated correctly.

Tracking down issues in the 32bit debug run, it turned out to be a memory
leak and the crashes were just memory errors that were not propagated
correctly.
@charris charris added the 09 - Backport-Candidate PRs tagged should be backported label Dec 18, 2023
@charris charris merged commit b9a0c9e into numpy:main Dec 19, 2023
61 of 64 checks passed
@charris
Copy link
Member

charris commented Dec 19, 2023

Thanks Sebastian.

@seberg seberg deleted the mem-errors branch December 19, 2023 06:15
@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Dec 22, 2023
@charris
Copy link
Member

charris commented Dec 22, 2023

@seberg I left out the mapping.c changes in the backport because they seem related to the dtype changes. Is that correct?

@seberg
Copy link
Member Author

seberg commented Dec 22, 2023

OK, I am not 100% sure, but the code looked a bt like it may have been changed recently (and it is a pretty minor thing anyway).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants