Ticket #10920 (closed: fixed)
New valgrind warnings after upgrade to NeXus 3.3 on RHEL
Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
---|---|---|---|
Priority: | major | Milestone: | Release 3.4 |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Federico M Pouzols |
Description (last modified by Martyn Gigg) (diff)
APITest has picked up some valgrind errors that originate in NeXus when moving to v4.3.3 on RHEL.
We need a new suppression to cover this:
{ <insert_a_suppression_name_here> Memcheck:Leak fun:malloc fun:strdup obj:/usr/lib64/libNeXus.so.0.5.0 fun:H5A_attr_iterate_table obj:/usr/lib64/libhdf5.so.6.0.4 fun:H5O_attr_iterate fun:H5Aiterate2 obj:/usr/lib64/libNeXus.so.0.5.0 fun:_ZN5NeXus4File11getNextAttrEv fun:_ZN5NeXus4File7hasAttrERKSs fun:_ZN6Mantid3API13PropertyNexus12loadPropertyEPN5NeXus4FileERKSs fun:_ZN17PropertyNexusTest24test_saving_then_loadingEv }
Change History
comment:3 Changed 6 years ago by Martyn Gigg
- Status changed from assigned to inprogress
Update valgrind suppression for new version of NeXus.
Refs #10920
Changeset: 52c868ba822dd00de3a9e8e85a5be5653c4f8e6d
comment:4 Changed 6 years ago by Martyn Gigg
Add new valgrind suppression for AlgorithmManager
It is no longer covered by the other suppression and was found while debugging the new warnings from NeXus. Refs #10920
Changeset: e70427c4276e177250f1fa57ed7b171977597794
comment:5 Changed 6 years ago by Martyn Gigg
- Status changed from inprogress to verify
- Resolution set to fixed
This is being verified as pull request #130.
comment:9 Changed 6 years ago by Federico M Pouzols
- Status changed from verify to verifying
- Tester set to Federico M Pouzols
comment:10 Changed 6 years ago by Federico M Pouzols
All looks fine and the 11 memory leak warnings have vanished away, so it works.
comment:11 Changed 6 years ago by Federico M Pouzols
- Status changed from verifying to closed
Merge pull request #130 from mantidproject/feature/10920_new_valgrind_supprs
Update Valgrind suppressions
Full changeset: 1382329252f790e1c4182aeade9fad6c662aad95
comment:12 Changed 5 years ago by Nick Draper
Somehow these slipped through without a resolution. Set to Fixed.
comment:13 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 11759