NUI Interface is crashing!

[ayazwai]

Describe the bug

• If you want to play more than one sound within 1 to 2 seconds, the entire NUI interface restarts itself due to xsound.

To Reproduce / To experience this

• Add the following code to any script's client.lua file
• Replace the music in the Soundlist with your own selected music or sound effects.

local list = {
    “test”,
    “test2”,
    “test3”,
    “ring”,
    “dong”,
    “ding”,
}
RegisterCommand(‘xsound’, function()
    for _, sound in pairs(list) do
        TriggerServerEvent(‘InteractSound_SV:PlayOnSource’, sound, 0.1)
        print((‘The sound is %s Playing’):format(sound))
        Wait(250)
    end
end)

Expected behavior

• Type xsound, and after the loop stops, observe a white image flickering on your screen for a few seconds. From this point on, you may notice that UI elements such as the phone, inventory, or HUD have disappeared and become unusable.

Screenshots / Videos
https://streamable.com/9tl257
https://streamable.com/yj0548

Additional context

[Xogy]

Before playing the sound effect

After testing with 150 instances of MP3

The issue won't be in xsound or at least this version of xsound. Make sure the xsound you are using is the newest because an increase of RAM that is about 4mb~ will not crash your UI.

• LB-Phone released an update: Soon, people will be able to hear all phone notifications and calls. After this update, this situation became even more popular.

If there is already a fix, then feel free to create a PR with the fix, as this is open open-source project.
If the issue persists, then you will have to provide code that will crash the UI and really make sure you are testing it in an empty environment with version 1.5.1 at least.

[ayazwai]

Thanks for the quick response.
I found that the large size of the OGG or MP3 files used and the fact that they are called multiple times simultaneously are causing this. Thank you! 🫡

[Xogy]

Thanks for the quick response. I found that the large size of the OGG or MP3 files used and the fact that they are called multiple times simultaneously are causing this. Thank you! 🫡

How big files are we talking about? are they mp3 or ogg?

[ayazwai]

I deleted the files, but I remember a few of them. There were OGG files that were 50 and 70MB in size. I have no idea why they use such large files..

[Xogy]

Those are very massive files... simply download AudaCity and just shrink them by exporting them again...

My other project with 176 sound effects is only 12mb, which is 70 KB per audio.. So having one sound effect being 50mb is very insane.

[ayazwai]

Yes, absolutely. Thank you again for your prompt response and for your time.

[Whisperisgod]

We are experiencing this problem too
It could also be one of the scripts that work with rcore audio.

[exotiicallstar]

Is their any new progress inside? We have the same issues since past days & we found a lot other servers with the same

[Xogy]

@exotiicallstar @Whisperisgod

Please read the comments, it this was issue of notification sound having 50-100mb per audio clip,

[exotiicallstar]

@exotiicallstar @Whisperisgod

Please read the comments, it this was issue of notification sound having 50-100mb per audio clip,

I am not sure if i understood it correctly in the comments here. We not using "own" music. Xsound is just in use for "Roadphone" wich only play music from youtube.

https://streamable.com/prjbfb

from what i can say, we have "exactly" the same issue since few days & i started some research and noticed that a hand full of other servers experiencing as well since few days exactly the same issue.

Something causing a cef crash, thats why websockets disconnecting.

As we continue to search for the cause, we found out that all of the projects have xdiskjockey and/or xsound in use.
We made some head snapshots and found issues related to it that some regex computation in javascript in a NUI or somewhere else causing a memory leak.

So far i just found some people wich mentioned xsound into their snapshots.

We have updated now from 1.5.0 to 1.5.1. But we got info from other servers, they still have the issue and they are already on 1.5.1.

as i have saw, this topic was closed 2 weeks ago, but most of us experiencing this issues just since past 2 days. So not sure if its exploit wich is shared on modding discords or anything else.

But for now it looks, like it comes from xsound or related to xsound. Thats why i asking here, Cause its simply exactly same issue what was reported here 2 weeks ago.

[exotiicallstar]

@exotiicallstar @Whisperisgod

Please read the comments, it this was issue of notification sound having 50-100mb per audio clip,

Oh now i understand what you mean. The report here was related to a notification sound, alright.

But since 2-3 days many other servers notice actually "same cef crashes" wich are not related to "own sounds". So it looks like somehow modders are able to create this cef crash for people on servers wich using xsound. We compared all the servers wich reported this and the only ressources wich all have are xsound.

But at all happening exactly same cef crash, as mentioned by thread creator here. Just with the difference its not related to own sounds. Most of them just have xsound because of phone or to play "youtube" music

Example from our server: https://streamable.com/prjbfb

[yellowdev777]

@exotiicallstar @Whisperisgod
Please read the comments, it this was issue of notification sound having 50-100mb per audio clip,

Oh now i understand what you mean. The report here was related to a notification sound, alright.

But since 2-3 days many other servers notice actually "same cef crashes" wich are not related to "own sounds". So it looks like somehow modders are able to create this cef crash for people on servers wich using xsound. We compared all the servers wich reported this and the only ressources wich all have are xsound.

But at all happening exactly same cef crash, as mentioned by thread creator here. Just with the difference its not related to own sounds. Most of them just have xsound because of phone or to play "youtube" music

Example from our server: https://streamable.com/prjbfb

My players are experiencing the same issue — completely random UI crashes, not for everyone, and it started around 3–4 days ago as well. Nothing in our resources changed on our side, so it really lines up with what others are reporting here.

[Xogy]

I did some testing and it seems to be issue related to either chromium or new youtube API changes.

3 months ago I had one ticket with something similar where xsound had an actuall memory leak but that was fixed

I will try to look for a workaround I MIGHT have something that could work but I do not promise anything yet

[exotiicallstar]

Thanks so much! I am happy you was able to reproduce the issue, cause i think a lot people still not noticed so far, that they actually have this issue as well. We have usally 150-200 people primetime and its as well just starting happening beginning from 150+ people. And additional i think not a lot people will be able to understand that they have a memory leak, cause people not really crashing. I think a lot servers thinking still, thats just a client related issue.

But basically what happening is:

• memory leak happen
• Fivem Chromium Subprocess raising up to 1,4Mb - 1,7MB
• than they get the cef crash without dropping from server
• because of the cef crash, the websockets disconnecting, thats why HUD is flashing up, and other UIs break

We researched 2 days to find other servers with the same issue and compare wich scripts all using same.

I am glad, that we found at all the cause. So its at all YT embeeds / API of youtube OR cfx updates. But as i heard from CFX, their was no CEF updates.

And its starting since 2-3 days, so most likely it will be YT API

Thanks for your time !

Best regards