No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Confirm in 2.0.5 on ubuntu 20.-4 when invoked with
benchmark-launcher-cli blender download (no version code added)

I cannot reproduce the issue. Does this still occur with the current Benchmark software?

Blender does not crash per se, it's Cycles that fails to render the scene and aborts the process.

If 2.90.1 and later works, then the issue has most likely been solved within the corrective release of 2.90.1. This would be easier to check with a full debug log and crash report.

Made some further testing by downloading multiple versions of Blender manually, and I found 2.90.1 and 2.91.0 no longer have the issue! The solution would thus be as simple as updating the Blender Benchmark Launcher with a 2.91 option, and perhaps blacklist the Victor scene with Blender 2.90 when rendering with the GPU.

After searching up similar issues from other people, I learned to use the Benchmark CLI tool, so now I have a detailed log from the moment in which rendering consistently fails:

Oh hey, this seems very similar to the issue I just reported while using an AMD card with OpenCL, T83431. No overclocking applied.

I just wanted to express my appreciation of the edit mode crosshair. I even used the Speedflow addon mainly because it displays the current mode in fat letters in the corner of the viewport but the crosshair change is so much better. Now you can tell if you are in edit mode even with disabled overlays and header.

There are systems in place to remove outliers, this is not considered a bug.

Are there updates on this?

There's been a new release of the Blender Benchmark in January 2020 as @Aaron Carlisle (Blendify) mentioned.

Please try again with the updated benchmark.

I tried the Victor scene with an unrelated Windows laptop with 16GB ram and it had the same result.

Hi @Sem Mulder (SemMulder), my apologies, I think I misunderstood what you said. I see the file now and yes, this works. Please accept my apologies for the inconvenience.

Hi @Sem Mulder (SemMulder), I wouldn't call this resolved because the core issue is still a problem. I did use poetry per the instructions. Did you mean the readme.md (as opposed to txt)? There's no txt file anyway. I will try running the launcher in debug mode, but I think it failed the last time I'd tried that.

I believe @Ray molenkamp (LazyDodo) is correct here. We are currently still investigating how to detect this properly (detecting the amount of GPU memory available across all brands is a bit complicated). Closing this for now as this is not an issue with the launcher per se.

This issue occurs because you first need to download the Blender version. Please read the README.txt included in the archive downloaded from opendata.blender.org for details. We might improve that error message here though. Since this is not a bug I am closing this issue.

@Sem Mulder (SemMulder) any idea what I'm doing wrong here?

Also the 'import snapshot' instruction in the documentation fails with:

So, regarding this note:

So I just tried running the test script (I didn't change the default values for the parameters mentioned above) and I get these errors:

How can I do this step:

peak memory for victor on my box is 16774.97M that 16GB of ram may be just a little short there.