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

fix minor ASAN issues in UMAPAlgo::Optimize::find_params_ab() #4405

Conversation

yitao-li
Copy link
Contributor

@yitao-li yitao-li commented Nov 24, 2021

There were actuall 2 minor issues that prevented UMAPAlgo::Optimize::find_params_ab() from being ASAN-clean at the moment:

  • One is the mem leaks, of course
  • Another one is the malloc()-delete mismatch -- only memory allocated using new or equivalent should be freed with operator delete or delete[]

Another issue that was also addressed here: exception safety (i.e., by using make_unique from C++-14)

Signed-off-by: Yitao Li yitao@rstudio.com

@yitao-li yitao-li requested a review from a team as a code owner November 24, 2021 18:02
@GPUtester
Copy link
Contributor

Can one of the admins verify this patch?

Signed-off-by: Yitao Li <yitao@rstudio.com>
@yitao-li yitao-li force-pushed the bugfix/umap-find-params-ab-asan-issue branch from 499bb3b to 3106f80 Compare November 24, 2021 18:09
@cjnolet cjnolet added this to PR-WIP in v22.02 Release via automation Nov 29, 2021
@cjnolet cjnolet added bug Something isn't working non-breaking Non-breaking change labels Nov 29, 2021
@cjnolet
Copy link
Member

cjnolet commented Nov 29, 2021

ok to test

1 similar comment
@cjnolet
Copy link
Member

cjnolet commented Nov 29, 2021

ok to test

Signed-off-by: Yitao Li <yitao@rstudio.com>
@cjnolet
Copy link
Member

cjnolet commented Dec 2, 2021

rerun tests

2 similar comments
@cjnolet
Copy link
Member

cjnolet commented Dec 4, 2021

rerun tests

@cjnolet
Copy link
Member

cjnolet commented Dec 6, 2021

rerun tests

@codecov-commenter
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (branch-22.02@ed0e58c). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff               @@
##             branch-22.02    #4405   +/-   ##
===============================================
  Coverage                ?   85.83%           
===============================================
  Files                   ?      236           
  Lines                   ?    19410           
  Branches                ?        0           
===============================================
  Hits                    ?    16660           
  Misses                  ?     2750           
  Partials                ?        0           
Flag Coverage Δ
dask 46.42% <0.00%> (?)
non-dask 78.76% <0.00%> (?)

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


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ed0e58c...4b4d368. Read the comment docs.

Copy link
Contributor

@zbjornson zbjornson left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Member

@cjnolet cjnolet left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for the contribution!

v22.02 Release automation moved this from PR-WIP to PR-Reviewer approved Dec 6, 2021
@cjnolet
Copy link
Member

cjnolet commented Dec 6, 2021

@gpucibot merge

@rapids-bot rapids-bot bot merged commit 5820133 into rapidsai:branch-22.02 Dec 6, 2021
v22.02 Release automation moved this from PR-Reviewer approved to Done Dec 6, 2021
vimarsh6739 pushed a commit to vimarsh6739/cuml that referenced this pull request Oct 9, 2023
…ai#4405)

There were actuall 2 minor issues that prevented `UMAPAlgo::Optimize::find_params_ab()` from being ASAN-clean at the moment:

- One is the mem leaks, of course
- Another one is the `malloc()`-`delete` mismatch -- only memory allocated using `new` or equivalent should be freed with operator `delete` or `delete[]`

Another issue that was also addressed here: exception safety (i.e., by using `make_unique` from C++-14)

Signed-off-by: Yitao Li <yitao@rstudio.com>

Authors:
  - Yitao Li (https://github.com/yitao-li)

Approvers:
  - Zach Bjornson (https://github.com/zbjornson)
  - Corey J. Nolet (https://github.com/cjnolet)

URL: rapidsai#4405
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CUDA/C++ non-breaking Non-breaking change
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

5 participants