Details
Description
This change, https://track.hpccsystems.com/browse/HPCC-23975 (merged into 7.10.0), introduced a window where the activity could stop and clear an object (iLoader), whilst the serialization code was still using it.
Related - the mergeStats helpers were inadvertently taking a copy of the shared object, and in so doing so linking (and later releasing) - see: HPCC-27606
Combined with this bug, it could cause heap corruption if the serializeStats call was linking as the stop() thread was destroying the object.
Fix is to ensure the iLoader.clear() is inside the critical section.
Attachments
Issue Links
- is duplicated by
-
HPCC-26807 Inquiry History Build(Unexpected process termination)
-
- Resolved
-
-
HPCC-26961 Upgrade to 7.12, hash join stopped working - suspected memory corruption in LZ4
-
- New
-
- relates to
-
HPCC-27606 mergeStats helpers for Shared<> objects should be based on a const reference, not a copy
-
- Resolved
-
-
HPCC-23975 Refactor Thor activities to use CRuntimeStatisticCollection serialization/deserialization
-
- Resolved
-