New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CEF Crash? #1705
Comments
|
No information, no reproduction steps, and no access to an environment this occurs on isn't going to help any issue get fixed no matter how many people it 'happens to' or how many servers are experiencing it. If anyone else has any reproduction steps or other info (crash dumps, ETW traces, etc.), sure, but I'm closing this issue report - note that this is distinct from locking, you can still reply - since it is not actionable in this state. |
|
I am still working on giving some type of reproduction steps to make this easier on your end. In the mean time - here is a log from when the user interface was refreshed, a crash did not occur here. CitizenFX_log_2022-11-17T024909.log Below, you will also see a screenshot of the same crash error from the issue I referenced above. At the time, I was unable to have this person present me with the crash dump from when this crash occured; but this issue is still occuring. With this being said, I will be able to receive the log when this is reported again. |
|
Im having the same issue. Have you fixed yours? |
|
After further testing, the interface & CEF refreshing issue was solved. This was caused by a poorly coded resource that had memory leaks. As for the crash report, I indeed thought that it may have had something to do with all of the NUI randomly reloading. I don't want to say it did; but we have not had any reports of the crash occuring anymore since the issue with the poorly coded resource was solved. |
|
|
We solved ours by removing scripts that are playing youtube thru xsound script. |
|
ok, I have stopped the xsound resource, could you also provide me with a discord for a more fluid communication ? |

Describe the bug:
Below you will find a couple of videos of what is occuring. In the first video, you can see the player stats in the bottom left, along with devtools opened to the right, when this "bug" occurs, everything refreshes on the users interface; causing devtools to crash, causing all scripts to reload their UI (which is why you see UI randomly popping up on the players screen). The debug tool crashing repeatedly when this occured made it damn near impossible to actually see what could be triggering this. In the second video, you will see the player stats in the bottom left disappear again, along with some other resources that use a UI just randomly pop up on the players screen, you will then see that the player is frozen & unable to actually do anything within FiveM. This is when they will then need to manually restart the application.
Steps to reproduce the behavior:
We were unable to find productive reproduction steps for this. This seems to occur randomly at different times, doing different things, and only seems to be happening when the server is at it's full capacity; 140/200. We had the server down for "maintenance" and had 7 people in the server for more than three hours, this "bug" didn't occur once during that time.
Evidence:
Video #1
Video #2
Additional context:
Here is another GitHub issue as a reference, this seems to be happening to a hefty amount of people. We originally thought a resource could be causing this, come to find out it was also occuring on another very large server. This was also occuring for them when the capacity was full; 140/200.
The text was updated successfully, but these errors were encountered: