Status heap corruption

I have had frequent crashes lately. Just recently I did cleared cache and removed mods, but when I tab trough several vehicles, like cones, BeamNG crashes, sometimes it gets to 3fps without much of CPU or GPU load when switching vehicle.

Does anyone has experienced such and do I do clean reinstall right away or in a moment?

 

Must try that, it really started today and seems to happen when there is more vehicles on map and when I alt tab out of the map it is 3fps, when I tab to other vehicle, it might get better, I think it started after a crash I got when I made jbeam of a bench and had bug in beamtype, but not sure.

Restarting computer might also be one to test.

Works fine with single vehicle, on map. Quite interesting behavior, but I try reboot, then do what you suggested and see if that clear the clog up from the pipes
--- Post updated ---
Okay, I did clean reinstall, completely everything from the scratch and I gained some performance as tabbing to another vehicle (cone) does not slowdown anymore, also alt tabbing did not cause 3fps anymore, did play quite few rounds of this map and car:
https://www.beamng.com/threads/beamng-automation-for-motorsports-training.58725/

As I kept tabbing to cones and pressing R, it did now again heap error, when tabbing to another cone beamng stopped responding and there was again this heap error.

Also I did install BeamNG and it's documents to another drive, to SSD now, no any other mods that those two linked were used.

It seems to be directly related to moment when I press tab key.

I don't quite understand what heap corruption means, so it is bit hard for me to know what is happening, might need to research that a bit to gain better understanding of potential causes.

 

Just a little update.

I did test today with lot of vehicles and I could not make this issue appear, only change I could see was that I had no Thrustmaster T150 wheel connected to computer. However I need to do more testing of this tomorrow to see if that would be cause of the issue and maybe find ways to reproduce it.

 

@Nadeox1 Here is something odd once again.

When I spawn 10-12 traffic cones and D15 on gridmap, I can tab trough them as fast as I want without drop in FPS.

When I have Thrustmaster T150 connected, I get drop in fps each time I press tab to switch from cone to cone, if I press tab really quickly, fps goes down to 1fps only.

Also when I have wheel connected, if I alt tab out of game, it sometimes locks game to 3fps and sometimes I get that heap corruption error when exiting game by alt-f4

However it only happens when T150 is connected.



Ah great, now they have updated version and thought I have latest, it was not long ago than I checked, so have to test again after a reboot, brb and all that...
--- Post updated ---
So new update to T150 wheel software and same thing is happening.

I can make BeamNG crash by having 10 large cones, then tab and r few times, not even really fast, but when T150 is not connected this does not happen.

It is something to do with physics I guess, because when game locks to 3fps pausing the physics bring fps back to 60fps, however unpausing brings fps back to 3fps.

I can cause locked to 3fps also happen when I copy cones in world editor without pausing the physics, but again only when T150 is connected.

Heap corruption error has not come up yet today though.

With gamepad such does not happen, but it is wireless rumble pad 2 and game disables ffb for it.
--- Post updated ---

 

No wheel connected:


With wheel connected:

 

I can get more if needed

Once for example game was running fine, I click exit to main menu (gridmap was loaded) and game did go to 3fps. Also there was some ffb related errors spawning on log once and wheel failed to have ffb then, not sure if related and has not happened again, but overall there seems to be lot of something with T150 wheel, maybe it is wheel's drivers causing it all, maybe something else, but interesting events happening with this plugged in.

Oh and pressing control R several times might make 3fps happen or cure it, or if done too quickly in sequence game crashes and sometimes heap error is presented after that, but not always, wonderfully annoying when trying to set needles to proper position, but also could be hard to figure out what is causing this issue, there is so much random to it.
--- Post updated ---
Happened in 0.14 too, used parts manager and as vehicle updates/loads FFB was nowhere, got this spammed to log incredible rate:

 

I got the same error with 2 default cars spawned and i think i had no mods enabled but i did have my Thrustmaster TMX connected.

 

T150 and T500 uses same driver, afaik, not sure if TMX uses same one too?

Does your game get to 3fps when alt tabbing out of it?
Mine does not always do but mostly does that, have to hit ctrl-r which usually cures that, but sometimes takes few attempts.

One important bit, I'm running game in Borderless window at desktop resolution, not sure if full screen alt tabbing works better, but my monitor is so awfully slow to switch modes that I prefer not to use full screen.

 

I meant the crashing

 

For me crashing happens after game starts to run 3fps, then I hit ctrl-r and sometimes it fixes fps, sometimes it causes crash. Without wheel plugged in none of such happens.

Update: Ah, they pushed hotfix already, let's see what happens with that
--- Post updated ---
After 1st update to 0.14 this situation is still the same, just for your information, there probably was not yet changes related to this.

3fps is not happening right after loading a level, it takes few times of alt tabbing or cloning lot of cones, usually, not sure if that is any value though, but it is hard to know what is, surprising things can help.

 

I did swap brake pads, front was fine, with rear a crash, seems to happen when vehicle is reloaded/physics activation.


Also locked to 3fps did happen once when unpausing physics, was fine before, I hit J to unpause physics and 3fps, ctrl-r fixed it that time.

So, I guess whenever there is a query for a wheel presence or something like that, something goes off. None of this happens when I have T150 wheel unplugged.

It is bit random how often this happens, feels like less in Windowed mode than in borderless window, difference might be just variance in frequency as sometimes stays away for tens of times, there is no absolute sure way to initiate this, except switching fast from vehicle to vehicle.

Maybe useless info, maybe useful, but you can analyze better with more data, I guess.
--- Post updated ---
Here is new bit of info, that might be relevant.

I did notice that search field like this is not taking inputs too well when T150 wheel is plugged in, when wheel is not plugged in, typing there did work fine (this might actually be Steam's fault, there was one checkbox steam defaults and I tampered with that, need more testing to tell if it was that or if there is just some randomity to it):

--- Post updated ---
This time 3fps did happen when I did drive trough final checkpoint of light runner nose dive stage, car goes trough 'gate' at the end and as I hit last checkpoint, very slightly after that everything slows down to 2-3fps, there is no any kind of hit of vehicle etc. I think only slowmotion should activate, but that was enough to trigger that 3fps thing or something completely other thing, it is so random.

Then as I did click retry slow fps continued, it took a while to get this much, but during this CPU load as well as GPU load are very minimal:


Now I'm not sure which of all these are related, they are things that happen at same time, things that happen only when my T150 wheel is plugged in, but this last one makes me go WTF literally. Common thing could be loading (for example loading high score table, loading vehicle, loading to menu), but why wheel would affect that, why only then it would happen that wheel is plugged in?

Hopefully you get better ideas.

 

0.14.0.2, 3 vehicles at ECA and I very slowly tab trough them as if I tab fast it gets very laggy, but still BeamNG crashed.


Also worth noting is that when I press J to pause physics it makes game run 3fps, while paused and when unpausing, ctrl-r revives fps back to 60, but tabbing trough cars can cause crash. Again only happens when T150 wheel is connected.

Also it is when pause is activated when 3fps starts, when unpausing it remains at 3fps.

It does not happen right away when game is started though, it requires some playing and happens sooner more vehicles are running.

For example I had Roamer and Covet, I set AI to random for Covet and had two runs without an issue, then 3rd run tabbing between vehicles became very slow, adding GM to game did not help at all, second run with 3 vehicles (two chasing one) caused tabbing to crash the game, before that I used pause and had to ctrl+r to fix 3fps that occured from pressing j to pause.

So some query to FFB wheel driver, but why 3fps starts when pausing game?


And typing issues to search field have not happened again after I disabled checkbox in steam.

There was one checked here, but can't remember which, Steam updated itself today and upmost was checked, even I cleared the page before, there should be ignore everything checkbox in Steam, makes just a mess:

 

So I did spawn 6 vehicles to JRI, fps got to 3 when I hit pause, ctrl-r did resume that, I drove maybe 5 minutes and then I did press tab to switch to other vehicle and I got a crash with heap corruption. Out of curiosity I did click debug option, but can't make out much of this:




Break is from point when I did hit debug I guess.

Not much new info really, just set FFB state and Command seem to be present there, but as this is from point after crash, not sure if it has any meaningful value, I guess that running with debug enabled would give some more info, but that is not possible, I think.

I got VStudio to crash by hitting restart button, maybe that could be classified as an achievement?

Anyway after hitting restart few times I got it to restart and also to crash so that VS did caught the crash, but I'm not getting anything out of it.


Something that might be of use is that within first minute from loading map and spawning 6 vehicles all is kinda ok, tabbing from vehicle to vehicle slows down each time pressing tab though.

Even pausing physics works for first minute quite likely ok.

After 2 minutes or more condition kinda deteriorates, after 5 minutes it is almost sure that pausing physics drops fps to 3 and tabbing from vehicle to another causes a crash within 1-5 key presses. So it acts like memory leak, but instead it is something else.


Most recent crash was with D15, but log here shows events at one crash before that:

Code:

1534.01685|D|libbeamng.lua.V.hydros.init|      smoothing = 80
1534.01688|D|libbeamng.lua.V.hydros.init|    },
1534.01690|D|libbeamng.lua.V.hydros.init|    ffbSendms = 1,
1534.01692|D|libbeamng.lua.V.hydros.init|    title = "X Axis"
1534.01695|D|libbeamng.lua.V.hydros.init|  }
1534.01697|D|libbeamng.lua.V.hydros.init|}
1534.01733|D|libbeamng.lua.V.hydros.init|Force Feedback motor found for steering hydro (physicsID: 13928, FFBID: 33, ForceCoef 140, ForceLimit 9.8, Smoothing 80, Period 2.5 ms / 400Hz (auto, ffbSendMs 1))
1545.37642|I|GELua.main|Player #0 vehicle switched from: id 13928 (vehicles/pigeon/) to: id 14009 (vehicles/pigeon/)
1546.09421|E|DirectInputDevice::sendForceFeedback|Failed to start FF effect: DIERR_INVALIDPARAM
1546.45948|E|DirectInputDevice::sendForceFeedback|Failed to start FF effect: DIERR_GENERIC

This is 'currently active' crash with 6 D15:

Code:

1671.71358|D|DirectInputDevice::setupForceFeedback|Using match found for player 0, desc 'xaxis', device 'wheel0', FFB axis 0, description 'xaxis'
1671.71364|D|DirectInputDevice::setupForceFeedback|Choosing axis 0 for FFB effects, with forceFactor: 1000.000000
1671.71369|D|DirectInputDevice::setupForceFeedback|setupForceFeedback: creating constant force feedback effect
1671.73072|I|GELua.main|Player #0 vehicle switched from: id 6776 (vehicles/pickup/) to: id 6824 (vehicles/pickup/)
1672.05843|E|DirectInputDevice::sendForceFeedback|Failed to start FF effect: DIERR_GENERIC

As both end to failed to start FF effect and as this crash occurs only with wheel connected, it would be very fitting, but of course there can be something else that triggers error in wheel.

Also as I did go trough the log, when 3fps did happen, there was this in log:
105.20889|E|DirectInputDevice::sendForceFeedback|Failed to start FF effect: DIERR_INVALIDPARAM

Interestingly when I went to game options and took checkmark off from box 'enable ffb' same error was logged and 3fps occurred.
However that did not go away until restart of the game.

After restarting tabbing was fast and there was no 3fps happening even wheel connected.

Setting Fast updates instead of full had no effect to this, but T150 wheel needs full updates or FFB is just really weird.

 

Today I moved computer to different spot and installed new printer, Canon PIXMA TS 3151.

For reasons unknown to me, there is no longer issue with switching between vehicles when wheel is plugged in.

I can tell that I did plug wheel to different USB port, but I did plug it into same port where it was originally and no issues. I did put computer to sleep and resumed, as that is how I usually have my computer, rarely do restarting, but no, issue stays away.

There really are no other changes made, I have same peripherals connected, same everything really.

I always unplug wheel after use too, so can't be anything there either.

There really are no other changes, so I'm not sure if printer installation can flush something or if plugging wheel to different port can flush something. Can there really be any other explanation?

 

Yeah, I had Epson XP-245 installed, but not plugged in.

After months of not being used I did test that printer and it had developed paper feed failure during that time, so I bought new one Canon PIXMA TS3151 for 22 euros from sale (never pay too much for a printer).

I did install that too using USB cable, I did not test wheel after moving computer to 3 meters different spot, did install this new printer and then as I tested wheel in BeamNG it did work without an issue.

I did plug wheel to different USB port though, that I had not done before I think, but now I can plug wheel to any USB port and I don't get these slow vehicle switch, low fps or crashing by heap corruption issues anymore.

It is really difficult to try to pinpoint what could possibly cause this as I still have Epson drivers installed, not any other updates have been made (I have all updating manual, even antivirus as diagnosing is easier that way, less variables).

What I think was happening is windows usb driver hiccup, but it still is bit odd.

Also today I found out that USB port (circled in red) next to one I usually plug wheel to, is not working too well, causes PC to crash if I plug wheel to that, but that has had issues of not working with Rumble pad receiver unit either in past, so hardware issue is not impossible either, but port next to one circled in red does work.


I did try all kind of things and so far no luck making issue coming back again. I wonder if that other user that had this issue, has managed to solve it already?

Now installing USB sound card did not fix this issue of mine, but after installing printer issue has disappeared, I'm just not certain if printer installation really had anything to do with it.

I did install also 1 more HDD to computer for better management of different installs etc. That should not have anything to do with the wheel issue though.


Other possibilities that have chance to cause such issue would be some pc freeze / crash and the fact that this Windows install had Z370 motherboard and i7-8086k installed too, but that motherboard was a dog and while I'm getting new one from warranty I'm looking for buying better for that and building 2nd pc but that takes time.

Anyway that or some crash could be one starting the issue, but I did not notice issue until I used B25Mitch's autocross map as usually I use single vehicle.

What did then fixed issue is a equal mystery, but those are highest probabilities with my limited understanding.

Really weird issues though and considering other user had similar with Thrustmaster wheel, so kinda would like to figure out more, but also bit difficult without that issue.

If I manage to find out how to cause the issue, then I could PM you about it as currently I have no ideas how to make it happen anymore, but anything is possible