Crashing after Loading Asset Heavy Worlds

TreeOnFire commented 3 years ago

Describe the bug?

When loading a world with a lot of assets in VR mode in Linux native or on Proton, it will crash the headset completely, crash/soft lock Neos and sometimes crash/soft lock Steam/SteamVR. Checking the GPU's VRAM, I am fine sometimes for a while with 4972MiB usage, until it spikes to 5140MiB+, which then my headset will black out entirely.

Neos can sometimes continue to run in the background on my monitor perfectly fine and Steam sometimes will display an error message saying to restart VR, but not all the time. For Proton, I used Proton 6.3-6.

I tested various worlds and it was when worlds that went past 3000 assets that ended up causing the hard crash. I have been to these worlds in Linux Desktop mode and encountered no problems save for having disabled desktop on the config file due to problems loading under Proton a few days ago.

Relevant issues

https://github.com/Neos-Metaverse/NeosPublic/issues/2698

To Reproduce

Load up Neos on Linux, using it under native or Proton.
Load an asset heavy world.
It will either crash instantly, or after 5-15 minutes of constant use.

Expected behavior

Loading an asset heavy world while in VR should not blackout my headset and continue to function as normal.

Log Files

error.log Player.log

Screenshots

No response

How often does it happen?

Always

Does the bug persist after restarting Neos?

Yes

Neos Version Number

2021.9.14.1024 and a few versions before it

What Platforms does this occur on?

Linux

Link to Reproduction Item/World

No response

Did this work before?

I Don't Know

If it worked before, on which build?

No response

Additional context

No response

Reporters

arx / arx#0001

Frooxius commented 3 years ago

What hardware are you running on? How much VRAM do you have?
What Linux distribution are you using?
Are the logs provided from Proton version? Do you have ones from native Linux version?
Do you have crash dump file?
Can you test your system memory to check if there are any errors?

The logs are completely missing stack trace for crashed thread. It almost looks like some memory corruption.

TreeOnFire commented 3 years ago

* What hardware are you running on? How much VRAM do you have?

AMD Ryzen 1700 GTX 1080 Ti (11GB VRAM) 32GB of RAM

* What Linux distribution are you using?

Pop!_OS 21.04

* Are the logs provided from Proton version? Do you have ones from native Linux version?

Those logs are from Proton, these are from the native build: DUMPSTERFIRE - 2021.9.14.1348 - 2021-09-15 00_29_12.log Player.log

* Do you have crash dump file?

Sent it there to Shifty.

* Can you test your system memory to check if there are any errors?

Will test now out and report back soon.

TreeOnFire commented 3 years ago

* Can you test your system memory to check if there are any errors?

Completed an over 15 hour memory test for RAM, it passed with 0 errors. Also ran GPU benchmarks and no flagrant errors either.

Neos-Metaverse / NeosPublic