ITS: GPU: reverse destruction order to fix crash#14863
ITS: GPU: reverse destruction order to fix crash#14863davidrohr merged 1 commit intoAliceO2Group:devfrom
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
Error while checking build/O2/fullCI_slc9 for 3bee3f7 at 2025-11-27 14:29: Full log here. |
|
Error while checking build/O2/fullCI_slc9 for 22bec1f at 2025-11-27 16:42: Full log here. |
Signed-off-by: Felix Schlepper <felix.schlepper@cern.ch>
22bec1f to
285872c
Compare
|
Error while checking build/O2/fullCI_slc9 for 285872c at 2025-11-27 22:27: Full log here. |
Fixes crashes in the GPU test:
The issue is that after #14681, I relied on the framework pointer being around when calling the TimeFrame destructor, which is fine when using the gpu framework held by the its reco workflow (
o2-its-reco-workflow --use-gpu-workflow). However, running in the real gpu-reco-workflow this is not the case. The framework allocator was destructed before the destructor of the TimeFrame was called (c++ clears them in reverse member declaration order). The solution is simply to reverse the member order.