ORNL / ORNL/ReSolve

Bug: 35/46 tests fail on ROCm when using address sanitizers.

Open
#388 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
84
Forks
13
PR merge metrics
No merged PRs in 30d

Description

Description how to reproduce the bug
cmake -DRESOLVE_USE_ASAN=yes -DRESOLVE_USE_UBSAN=yes -DCMAKE_BUILD_TYPE=RelWithDebInfo -DRESOLVE_USE_LUSOL=yes  -DRESOLVE_USE_KLU=yes -DRESOLVE_USE_HIP=yes -DCMAKE_INSTALL_PREFIX=../install ../ReSolve/
make -j
ctest -j

Memory leaks such as:

Indirect leak of 192 byte(s) in 2 object(s) allocated from:
    #0 0x00000035618d  (/autofs/nccs-svm1_home2/regevs/ReSolve_dir/build/tests/functionality/sys_rand_gmres_test.exe+0x35618d)
    #1 0x7fcac46ded82  (/opt/rocm-6.4.0/lib/llvm/bin/../../../lib/librocsparse.so.1+0xc21d82) (BuildId: 5343bf0c81290fba73afda9c5bcff0800301e5e2)

Indirect leak of 64 byte(s) in 2 object(s) allocated from:
#0 0x00000035618d (/autofs/nccs-svm1_home2/r


The same errors do not appear when the address sanitizer is not enabled, or alternatively during CPU only builds.

### Re::Solve version

All versions

### System and environment details

Build environment:
  - Frontier
  - rocm 6.4
  - gcc 12.3

### Additional information

_Verified as AMD's error._

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the provided CMake options on Frontier using ROCm 6.4, then run ctest -j and inspect the failures, including functionality/sys_rand_gmres_test.exe. Determine whether the reported sanitizer leaks originate in ReSolve or the ROCm libraries; done requires resolving or clearly isolating the 35 failing tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.