15-06-2026, 08:08 AM
(This post was last modified: 15-06-2026, 08:08 AM by josemendez.)
Hi!
Could reproduce the issue. The correct fix is indeed to add a null check in OnEnable() and don't create a new handle if there's one already around.
Note this affects versions prior to 7.1.1 as well, but since the issue only appears when a specific ordering of OnEnable calls takes place, it may not happen unless these specific conditions are triggered.
Thanks for reporting this!
Could reproduce the issue. The correct fix is indeed to add a null check in OnEnable() and don't create a new handle if there's one already around.
Note this affects versions prior to 7.1.1 as well, but since the issue only appears when a specific ordering of OnEnable calls takes place, it may not happen unless these specific conditions are triggered.
Thanks for reporting this!