There is an AWFUL refresh loop happening in the Avatar Descriptor if inspecting your Avatar in Editor Mode or Play Mode, specifically with Face Tracking section expanded with many mapping rows exposed (all ~102).
My Findings:
  • FaceTrackingEditorContext.Tick
    increments every
    EditorApplication.update;
    , the
    ParameterBehavior
    and
    BlendshapesSet
    drawers treat a new Tick as invalidation, so their per-element state and validation refresh on every editor frame.
  • FaceTrackingBlendshapesSetDrawer
    draws ALL ~102 mapping rows insaide a 280px scroll view with no visibility culling.
  • Every
    EditorApplication.hierarchyChanged
    bumps
    HierarchyRevision
    , causing
    CollectAmbiguousMeshPaths
    to run
    GetComponentsInChildren<Transform>(true)
    and
    CalculateTransformPath
    on EVERY transform of the Avatar on the next repaint.
  • Cost scales with the number of Parameter Behaviors (in my testing, I had 38). Tools that add Parameter Behaviors in Play Mode like VRCFury or NDMF make this behavior much worse.
My suspicions believe this has gone unnoticed since most users utilize non-destructive tools like VRCFury or NDMF to add the Parameter Behaviors and Face Tracking instructions at upload time. Either way, if this scenario is caused normally, it is a severe performance issue that should be addressed.