What causes a frame-time spike of unknown origin in Godot?

One function is doing too much work on certain frames, but Godot's debugger shows the aggregate timing so the spike's cause is hidden among many script and engine calls.

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 Find a Frame-Time Spike With the Godot Profiler and Debugger

Quick answer: Open the Debugger's Profiler tab, record while reproducing the spike, sort functions by self time, and drill into the top script function, confirming with the Monitors graph and targeted print timing.

Godot's editor includes a profiler that most people never open. When the frame rate hitches, it can tell you which _process or _physics_process function ate the frame, turning a vague stutter into a named function you can fix.

How to find it

1. Record in the Profiler tab

Open the bottom Debugger panel, go to Profiler, and click Start while you reproduce the spike. It captures per-function time across frames for both script and engine functions.

2. Read self time, not total

Sort by Self time so you see the function actually consuming the frame rather than parents that merely contain heavy children. The self-time leader is your spike.

3. Cross-check with Monitors

The Monitors tab graphs process time, physics time, draw calls, and object counts. A spike in physics versus process versus draw tells you whether the cost is logic, simulation, or rendering before you dig into code.

4. Confirm with targeted timing

Wrap the suspect function in Time.get_ticks_usec() measurements and print the delta. This verifies the profiler's finding and shows how the cost varies with game state.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.