Item data is undefined (CEF crash / memory leak)

[ProjectRogueRP]

Describe the bug Im getting a global issue reported by players where they are reporting that they are randomly just getting their inventory scuffed. No errros, no nothing. Just breaks. The images disappear, they cant use or do anything with their inventory. They simply just disconnect and then it fixes it. Any issues what could be causing this issue? Randomly started happening around the time the crafting was introduced? I also asked a couple other server owners, and they said they were experiencing this as well, using ox_inventory. Im just baffled that I dont see any forum post about this yet, as its been happening for a bit now. Any ideas, recommendations, or even right directions to test, im willing to do them! Thanks guys

PLAYERS REPORT: “whenever i hang out in the city for a few hours my inventory just turns into this and doesnt let me use any items or interact with anything in the city as soon as i see this. if i dont open my inventory i can still use the "front pockets" and interact with things around the city but as soon as i open it and see this its done. There is no clear indicator on when it happens other than opening them and seeing this”.

To Reproduce Steps to reproduce the behavior: Im unsure, but was asked by Luke to open this on github!

Expected behavior For it not break while they are playing

Screenshots

[ProjectRogueRP]

@LukeWasTakenn

[fivemservergg]

I have the same problem, is there a way to solve it? Other scripts related to the UI will also have problems when the inventory is reset.

[thelindat]

This is something related to CEF as a whole rather than the inventory. It’s not impossible that there’s an issue in ox inventory, but so far people have reported that xsound is causing a memory leak or something.

Other scripts related to the UI will also have problems when the inventory is reset.

Basically affirming that the inventory is broken, but it’s not the only thing experiencing problems and is not necessarily the cause.

---

You can see if the issue doesn’t occur with the recent crafting update, as the timing is there; but is likely a coincidence since CEF was updated in the past few weeks.

[Smailas01]

I have same problem any fixs ?

[thelindat]

I have same problem any fixs ?

but so far people have reported that xsound is causing a memory leak or something.

https://github.com/overextended/ox_inventory/issues/986

[ProjectRogueRP]

Hi there. So in more testing, I was hoping xsound was going to be the issue breaker! However, I have disabled all scripts using xsound along with the xsound resource, and the UI is still crashing! I just figured I would give the report that its still happening, even without xsound! So my only thought now, is that it has be the inventory or a FiveM Update messed something up. Im not sure!

[thelindat]

I have disabled all scripts using xsound along with the xsound resource, and the UI is still crashing! I just figured I would give the report that its still happening, even without xsound!

Why is xsound mentioned in the console if it's disabled?

[luthanirgi]

Hi there. So in more testing, I was hoping xsound was going to be the issue breaker! However, I have disabled all scripts using xsound along with the xsound resource, and the UI is still crashing! I just figured I would give the report that its still happening, even without xsound! So my only thought now, is that it has be the inventory or a FiveM Update messed something up. Im not sure!

Hi there. So in more testing, I was hoping xsound was going to be the issue breaker! However, I have disabled all scripts using xsound along with the xsound resource, and the UI is still crashing! I just figured I would give the report that its still happening, even without xsound! So my only thought now, is that it has be the inventory or a FiveM Update messed something up. Im not sure!

update your xsound https://github.com/Xogy/xsound/releases/tag/1.4.2

[thelindat]

Haven't seen anybody mention this in a month so I'll just assume whatever it was has been resolved elsewhere.

[thelindat]

Apparently lb-phone had a memory leak, and three people have reported that updating it resolved this issue.

[Flek26]

I have this same issue. We Dont use lb-phone