How to Fix Server Thread Hitch Warnings

A server thread hitch warning means a server frame took longer than expected. One warning during startup is different from repeated hitches during play. Capture the workload and identify the delay before replacing hardware or disabling resources.

The configuration and code examples here target FiveM for GTA V Legacy. Enhanced has different runtime and compatibility rules; check Cfx.re’s Legacy-to-Enhanced changes before applying them to an Enhanced server.

Establish when the hitch happens

Record the warning, its timestamp, player count and the action taking place. Note recent resource or configuration changes. Compare startup, an idle server and the gameplay action that triggers the problem. Check host CPU, memory pressure and disk activity at the same time.

Capture the server workload

Run these commands in the FXServer console or the server console in txAdmin. The number is frames, not milliseconds.

profiler record 500
profiler status

Wait until the recording has completed, then inspect it:

profiler view

For a server capture, copy the viewer link into your browser. Keep the recording focused on the problem. Look for long-running resource code around the slow frames; also investigate host contention or blocking work when the warning has no matching script spike.

Make one evidence-based change

If the capture points to a resource, inspect the relevant loop, event handler or data access. Repeated work may belong in an event or a less frequent update; expensive queries need query-specific investigation. Do not increase waits in per-frame game-control code blindly.

Disable an optional suspect resource only on a test copy and check its dependencies first. Update artifacts using the documented runtime update procedure; a generic git pull does not update every FXServer installation.

Verify the result

Repeat the same action under a comparable workload and capture another profile. Check hitch frequency and duration together with the player experience. Restore the change if it breaks gameplay or does not address the measured cause. A client FPS problem or network delay needs its own investigation.

Reference

Cfx.re profiler guide