Skip to content

FIX: Fix table destructor not being called #2540

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

david-cortes-intel
Copy link
Contributor

@david-cortes-intel david-cortes-intel commented Jun 12, 2025

Description

ref #1869

This PR fixes an issue with the destructor for table objects not being called when the python objects are deallocated.

The fix needs to be tested more thoroughly through sanitizers and valgrind when possible.


PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.

You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).

Checklist to comply with before moving PR from draft:

PR completeness and readability

  • I have reviewed my changes thoroughly before submitting this pull request.
  • Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
  • I have added a respective label(s) to PR if I have a permission for that.
  • I have resolved any merge conflicts that might occur with the base branch.

Testing

  • I have run it locally and tested the changes extensively.
  • All CI jobs are green or I have provided justification why they aren't.

@david-cortes-intel david-cortes-intel added the bug Something isn't working label Jun 12, 2025
Copy link

codecov bot commented Jun 12, 2025

Codecov Report

Attention: Patch coverage is 60.00000% with 2 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
onedal/datatypes/numpy/data_conversion.cpp 66.66% 0 Missing and 1 partial ⚠️
onedal/datatypes/table.cpp 50.00% 0 Missing and 1 partial ⚠️
Flag Coverage Δ
azure 79.84% <ø> (ø)
github 73.65% <60.00%> (+0.04%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
onedal/datatypes/numpy/data_conversion.cpp 53.02% <66.66%> (+1.86%) ⬆️
onedal/datatypes/table.cpp 51.92% <50.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@icfaust icfaust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to adapt this PR into #2364 and see if it helps some of the memory leak fails. Because this affects return values regardless of the inputs, I think it might also address this sporadic k-Means failure. Just a small change but otherwise I expect its basically good to go.

Co-authored-by: Ian Faust <icfaust@gmail.com>
Copy link
Contributor

@icfaust icfaust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately didn't solve the issues in #2364 . Looks good to go (just verify with a private CI run before merge).

@david-cortes-intel
Copy link
Contributor Author

/intelci: run

@david-cortes-intel david-cortes-intel marked this pull request as ready for review June 16, 2025 10:26
@david-cortes-intel
Copy link
Contributor Author

/intelci: run

@david-cortes-intel
Copy link
Contributor Author

/intelci: run

1 similar comment
@david-cortes-intel
Copy link
Contributor Author

/intelci: run

@icfaust
Copy link
Contributor

icfaust commented Jun 18, 2025

@david-cortes-intel please merge in main and re-run private CI

@david-cortes-intel david-cortes-intel force-pushed the fix_uncalled_destructor branch from f4d73ae to 51ac59c Compare June 18, 2025 14:32
@david-cortes-intel
Copy link
Contributor Author

/intelci: run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants