Page MenuHomeFeedback Tracker

YAAB Crashes since 2.02
Need More Info, NormalPublic


Frequent A3 crash to desktop while running YAAB since updating to 2.02 (147284)


Operating System
Windows 10 x64
Operating System Version
Windows 10 Pro 20H2 Build 19042.804
Game Crash
Steps To Reproduce

Load the vanilla game
Run YAAB scenario
(Click S to force standard settings.)
Repeat if necessary.

Additional Information

Pre-2.02, I have had absolutely no crashes while running YAAB.
I'm running the same PC/BIOS settings today as I have for about a week.
I was about to start some more tuning and decided to re-benchmark before starting in case 2.02 gave different overall performance.
Benchmarks are all run with the Vanilla game.
I've run a mix of 1080p and 1440p runs, all with standard graphics settings so far.
About 50% result in a crash to desktop.

I'm running the CMA memory allocator with large pages enabled but up until today, this does not seem to have been an issue. I've not yet tried without this enabled.

Crashdump should be attached

Event Timeline

run YAAB several times with CMA malloc after 2.02 and no crashes/problems

dedmen changed the task status from New to Need More Info.Feb 24 2021, 10:40 AM
dedmen added a subscriber: dedmen.

It looks like a memory allocation issue.
Please try not using -malloc=cma_x64

A series of runs this morning - only about 12 so far but I'll try to get time to run more if possible.
No crashes so far with cma_x64 turned off either 1080p or 1440p

1 crash so far with cma_x64 enabled at 1080p but several complete at both 1080p and 1440p. So much better success rate than yesterday when it was about 50% crashing.

Purely for interest but might also be useful info - enabling cma_x64 gives about a 10% fps improvement at 1440p but almost nothing at 1080p. At standard graphics settings, both resolutions are getting around 78fps average. I've not done enough runs so far but 1080p might be 1-2fps or so higher.

One thought is whether the crash is not cma_x64 related itself, but more when part of the YAAB is above a certain frame rate that I get the crash? That said, from what I've seen so far, I don't think the crash is occuring at the same point of the benchmark each time - although I've not watched them all.

Managed to run 15 more benchmarks this afternoon - all 1080p Standard settings as this seams the least stable. (Strangely.)

10 runs were with cma_x64 enabled. The first 7 completed fine, the next two both crashed and the final one ran through OK

I then intended to run 10 with cma_x64 disabled. However, the 5th one crashed so I think we can say that cma_x64 is not the cause.

As stated previously, up to 2.02, I'd never had any YAAB crashes (in probably a few hundred runs) so something does seem to have changed in 2.02 - at least in how it runs on my machine.

10 more runs at 1080p Standard with CMA enabled (as this seemed the least stable overall)
This time with the latest performance exe.
No crashes so far