> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/troubleshooting/crashes-performance.md).

# Game crashes, freezes or slows down

Identify the trigger and distinguish client, server, script, and streaming issues.

## Identify the symptom

| Observation                              | Record                                                   |
| ---------------------------------------- | -------------------------------------------------------- |
| One client closes                        | Crash message, time, action, and client log              |
| Several clients crash during one action  | Model, location, component, and reproduction steps       |
| Server process terminates                | Complete final server log, startup time, and last change |
| FPS drops while the server keeps running | Location, player/entity count, and affected clients      |
| Script execution time increases          | Comparable-load measurement and resource involved        |

## Build a repeatable test

1. Save logs and versions before replacing files.
2. Repeat the exact action on your test server: spawn, enter, collide, equip, or open a menu.
3. Use the untouched package and only its required dependencies.
4. Add other resources gradually and record the combination where the issue returns.
5. Compare with another client and another model or simple reference action.

A failure in an isolated test and a failure only with many streamed assets are different cases.

## Measure performance

Compare the same scene before and after the change. For scripts, use suitable tools such as the [Cfx.re Profiler](https://docs.fivem.net/docs/scripting-manual/debugging/using-profiler/). A single FPS number without scene, load, and comparison is not enough.

For vehicles and peds, visible models, texture volume, and streaming conditions also matter. Low script execution time does not rule out a model or streaming issue.

{% hint style="warning" %}
Do not raise pool sizes or change server/game settings without identifying the cause and checking requirements. A setting that helps another server is not automatically a requirement for your product.
{% endhint %}

## When to contact support

If the untouched package still fails with its required dependencies, send clear reproduction steps. For a vehicle crash, include speed, collision, extras, and tuning state where relevant.

[Prepare a ticket with logs](/studioworks-docs/support/preparing-a-ticket.md).

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://studioworks.gitbook.io/studioworks-docs/troubleshooting/crashes-performance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.