[Bug] Resource Monitor (resmon) causes client crash after ensuring a resource.

[deenz-dev]

Summary

On FiveM for GTA V Enhanced, restarting a resource while the Resource Monitor (resmon) is open causes the client to crash.

The issue does not appear to be related to any specific resource. I have tested restarting different resources and the same behavior occurs.

There is also a second way to reproduce the crash: if resmon is closed while restarting the resource, the client does not crash immediately. However, opening resmon afterwards causes the client to crash.

This makes it look like restarting/stopping a resource while using Resource Monitor leaves the profiler/resource monitoring state in an invalid state.

Issue type

Client

Repro rate

Always

Server build version

b161

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

Method 1:

1. Join a server on FiveM for GTA V Enhanced.
2. Open F8.
3. Run resmon 1/Open resources monitor.
4. Restart any running resource.
5. The client crashes.

Method 2:

1 .Join a server on FiveM for GTA V Enhanced.
2. Make sure Resource Monitor (resmon) is not running.
3. Restart any running resource..
4. The client remains connected and does not crash.
5. Immediately after the resource has restarted, open Resource Monitor/resmon 1.
6. The client crashes.

If enough time is allowed to pass after restarting the resource before opening resmon, the crash does not appear to occur.
The exact time window has not been determined yet.
The specific resource being restarted does not appear to matter.

Expected Behavior

Resources should be able to be stopped/restarted while Resource Monitor is running without crashing the client.

Likewise, restarting a resource while Resource Monitor is closed should not cause the client to crash when resmon is opened afterwards.

Actual Behavior

If Resource Monitor is already running, restarting a resource causes the client to crash.

If Resource Monitor is not running, the resource can be restarted normally, but opening resmon afterwards causes the client to crash.

Additional Context

This appears to be specifically related to Resource Monitor / resmon and resource lifecycle changes.

Restarting the same resources without Resource Monitor enabled does not immediately crash the client.

This may be related to Resource Monitor retaining or accessing profiling/resource data belonging to a resource that has been stopped or restarted.

Evidence

No response

Additional Context

No response

[Gogsi]

Hello,
A fix for this issue has been implemented in November 11 patch for FiveM for GTAV Enhanced. Please try again and let us know if the issue persists. Thanks for your help!

[deenz-dev]

Hello,
I can confirm that the issue has been resolved with the November 11 patch. Everything is now working correctly as expected.
Thank you for addressing the issue and for your work on the fix!

Best regards.