Quick answer: Unity UI Toolkit two-way binding causing a storm of updates? Setter triggers getter triggers setter - break the cycle with an updating flag.

Slider bound to a value; value bound to a label; label change re-triggers the slider. Infinite loop.

Use an updating flag

bool updating;
void SetX(int v) {{
  if (updating) return;
  updating = true;
  ...
  updating = false;
}}

Guards re-entry. Cycle terminates.

Or one-way binding

If the cycle isn't necessary, downgrade to one-way. Simpler; no storm risk.

Use property changed events deliberately

Don't subscribe in both directions. Pick the direction of truth.

“Two-way bindings have cycle risk. Guard or restructure.”

Audit two-way bindings in your UI. Each is a candidate for the storm pattern; not all need to be two-way.

Related reading