What causes slow UI from canvas rebuilds?

Changing any element on a UI canvas can force the whole canvas to rebuild its geometry, and animating or updating elements every frame triggers constant expensive rebuilds.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Slow UI Performance from Canvas Rebuilds

Quick answer: Split static and dynamic UI onto separate canvases, avoid changing layout-affecting properties every frame, and disable raycasts and layout components you do not need.

UI is a surprising source of frame drops because a small change can rebuild an entire canvas. Isolating what changes keeps it cheap. Here is how.

How to fix it

1. Separate static and dynamic UI

Put frequently-updated elements (timers, health bars) on their own canvas so changing them does not rebuild the static UI. One canvas for everything means every change rebuilds the whole thing.

2. Avoid per-frame layout changes

Changing size, text, or layout-group contents triggers rebuilds. Update only when the value actually changes, and avoid layout groups for elements that change every frame.

3. Trim raycasts and components

Disable Raycast Target on non-interactive graphics and remove unnecessary layout and content-size components. Each adds cost to rebuilds and input processing.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every your game error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.