Crippling Memory leak (0.31)

Not sure how to get the dev's attention with this one. Sure there are a lot of bugs I could report on despite having this game for only a month but this one's particularly critically special and repeatable in that it causes a crippling memory leak that absolutely kills windows operating system.

Method to replicate:
Duplicate, edit an existing or create a new vehicle with a new configuration for a vehicle with cargo boxes already mounted.
Remove the method of mounting the cargo box without actually removing the slot associated with mounting the cargo box.
Alternatively you can try to mount a cargo box to a slot that it doesn't recognise.
Then try to apply the cargo box.

Operating system will now shit itself so badly that your non-PS/2 peripherals fail to register input.

I discovered this bug several weeks ago when trying to mount a cargo box onto a modded vehicle (and eventually succeeded by using roofbars) and is specific to how cargo boxes work as far as I know since the game engine catches the issue and spits an error if you try to load a part with a missing prerequisite part.

Error output of the game engine, given enough time (about half an hour for me which is abnormally long considering how decently well beamng actually runs on my somewhat outdated system) is simply "System Error" but fails to close.

There are no error logs for this kind of issue because the game engine simply can't print anything while trying to find out where/how to spawn the cargo box.

 

Another way to replicate it on vanilla career is by doing uhh, trying to attach a receiver hitch to a van that's been upfitted with the cargo box in this glitchy arrangement

but yeah it seems to be an issue with trying to fit a universal part to a slot when the parent's slot mounting location isn't known or something (in the previous example it was because I tried to fit a cargo box to a vehicle without roofbars to attach them to)

 

That's so weird I haven't had that issue. What version of windows are you running?

 

yeah, this took my beefy Alienware laptop down twice to the point of forcefully shutting it off via the power button.

 

Have noticed same in multiplayer mod, after 4h beamng will give me warning my 64gb memory is almost full

 

Even running proton on linux it still happens.
https://www.reddit.com/r/BeamNG/comments/1awfc7v/not_even_my_new_beefy_3k_computer_can_stand_up/
--- Post updated ---

Figured I should upload the image here rather than using a temporary discord image link because they will expire eventually
--- Post updated ---

It's not even BeamMP related. I don't even have BeamMP's files in my 0.31 directory.

Try recreating it yourself. Put the truck nuts/fasterners/whatever the heck they are on the cargo upfit H series. It's a reliable way to end your operating system momentarily.

This problem can be recreated with ANY part that attempt to create a beam to a non-existing node string that would normally exist under different circumstances.
--- Post updated ---
Also to anyone who says taking a screenshot isn't hard (I've been told this 3 times in the past 24 hours thanks): You can't when your computer's bricked, that's like telling someone to screenshot their blue screen of death. That's how bad this issue is and why it is a CRIPPLING critical issue. Devs, please fix, this is a major game engine issue.

Parts not finding an attatchment point? Fair enough, spit out an error. But it shouldn't kill the operating system.

 

guess im not the only one, in the main menus and in game the memory leak got worse and it is now eating all of my ram

 

sorry for bumping the thread but the crippling memory leak needs to be fixed

 

are you still on 0.31?

 

not anymore since it has been updated to 0.35, but we had rough times on 0.31