Add more tracing events and logging for WebVR/Desktop |
|||||||||||||||
Issue descriptionTracing events and logging can be used to diagnose performance issues or investigate some bugs. When users report issues like "presentation doesn't work" or "controllers weren't responding" a trace could identify why things aren't working. When users report something is slow, tracing events could give a hint at what specifically is slow, and why.
,
Jul 4
,
Jul 4
,
Jul 12
,
Jul 12
,
Jul 12
,
Jul 12
,
Jul 16
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
,
Aug 7
Removing Internals>VR component and assigning to Internals>XR
,
Aug 7
,
Sep 27
Ideally, we'd be able to record causes in a more user-accessible way. For example, telling users to copy the contents from a page like chrome://xr (issue 803644).
,
Dec 6
|
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by tiborg@chromium.org
, Feb 2 2018