Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
scr-1.8.0
-
None
Description
When activating a component, the AbstractComponentManager#activateInternal method checks some properties, then grab the lock and actually activate the component, leaving a gap between the check and the lock being acquired, which can result in the component being deactivated in the mean time, ultimately leading to NPE because m_tracker has been nulled.
Attachments
Issue Links
- is related to
-
FELIX-4313 Bad synchronization in scr where a lock is held while ungetting a service
- Closed