Quick answer: Store yaw and pitch as scalars and rebuild the basis from scratch each frame instead of multiplying deltas into the existing transform.
An orbit camera whose horizon gradually tilts as you rotate around is accumulating roll from incremental basis multiplication. Rebuilding orientation from angles each frame removes it. Here is how.
How to fix it
1. Keep yaw and pitch as floats
Track the orbit with two scalar angles. Each frame construct the basis as Basis(Vector3.UP, yaw) * Basis(Vector3.RIGHT, pitch) rather than rotating the previous basis.
2. Rebuild, do not accumulate
Avoid transform.basis = transform.basis.rotated(...) every frame; the repeated multiplication drifts and adds roll. Always derive the basis from the canonical angles.
3. Orthonormalize if needed
If you must compose incrementally, call transform.basis = transform.basis.orthonormalized() periodically to remove accumulated skew and scale error.
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 Godot 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.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.