PengZheng commented on issue #647: URL: https://github.com/apache/celix/issues/647#issuecomment-1727204925
To be honest, it is really annoying to see any ASAN report on the framework (pubsub ASAN report is more acceptable), especially in the last minutes before a shiny new release. After `celix_scheduledEvent_create` returns a newly created event, ASAN reports that we are trying to read its ID via `celix_scheduledEvent_getId` from a freed memory region. From its size, it is most probably a Schedule Event. From the logging, we can tell there is only one ScheduleEvent ever existing: the first one-shot event. I re-checked the event handling path, and found no double-free. After the framework startup, there is no further dynamic memory allocation/deallocation except for ScheduleEvent, thus it is not the framework who deallocated a newly created event. The interesting part is ASAN does not report use-after-free within `celix_scheduledEvent_create`, which initialized the event. From what I saw, it does not seem like a Celix bug. But let's watch for a longer time if it reproduces. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@celix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
