You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The xr.xml defines the parent of XrSpace as the XrSession, but the text states that the XrAction is the parent of the XrSpace created by xrCreateActionSpace for purposes of implicit destruction.
Handles form a hierarchy in which child handles fall under the validity and lifetime of parent handles.
which would imply all XrSpace objects would be destroyed when the parent XrSession is destroy.
In contrast, this body text for xrCreateActionSpace states :
The XrSpace handle must be eventually freed via the xrDestroySpace function or by destroying the parent XrAction handle.
Does this imply that XrSpace created by xrCreateActionSpace remains undestroyed after xrDestroySession is called, and not destroyed as all other XrSpace handles created with xrCreate.*(XrSession session, ...)? Or is it saying the destruction of either the XrAction or the XrSession will cause the implicit destruction of created XrSpace?
The text was updated successfully, but these errors were encountered:
That is an error in the spec, the parent is XrSession for all XrSpace handles. There is text somewhere that says how an action space behaves after destroying the action, iirc.
An issue (number 2395) has been filed to correspond to this issue in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#2395 ), to facilitate working group processes.
This GitHub issue will continue to be the main site of discussion.
The xr.xml defines the parent of XrSpace as the XrSession, but the text states that the XrAction is the parent of the
XrSpace
created byxrCreateActionSpace
for purposes of implicit destruction.From the registry
XrSpace
is defined:<type category="handle" parent="XrSession"><type>XR_DEFINE_HANDLE</type>(<name>XrSpace</name>)</type>
thus be subject to the general
which would imply all
XrSpace
objects would be destroyed when the parentXrSession
is destroy.In contrast, this body text for
xrCreateActionSpace
states :Does this imply that
XrSpace
created byxrCreateActionSpace
remains undestroyed afterxrDestroySession
is called, and not destroyed as all otherXrSpace
handles created withxrCreate.*(XrSession session, ...)
? Or is it saying the destruction of either theXrAction
or theXrSession
will cause the implicit destruction of createdXrSpace
?The text was updated successfully, but these errors were encountered: