Asset Library crashing Blender on start up randomly #119722

New Issue

Steve-Wang · 2024-03-21T01:58:37+01:00

Steve-Wang commented

2024-03-21 01:58:37 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
Randomly, when I start Blender my ram usage will slowly ramp up until an eventual crash. This has been happening since 3.5, and I say "randomly" because 1/4 of the time it will work fine. I know this because the ram usage doesn't climb up at start up. As you can see in the attached image, default scene with a default cube can trigger this. Sometimes when this happens, even after Blender crashes, the task manager still shows a Blender client running.

I highly suspect that this is asset library related because I did a clean install today to solve this issue and everything was perfectly fine until I started installing the asset library paths back in.

If the crash doesn't happen right away at start up, then I am safe to work on that file until I try to open it again.

Exact steps for others to reproduce the error
I have years of asset library saved up and potentially hundreds of GB of models and textures within it. So for me to reproduce the error, all I need to do is open Blender and chances are it will crash. Due to this, it is impossible for me to provide a blend file that is usable.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.86 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** Randomly, when I start Blender my ram usage will slowly ramp up until an eventual crash. This has been happening since 3.5, and I say "randomly" because 1/4 of the time it will work fine. I know this because the ram usage doesn't climb up at start up. As you can see in the attached image, default scene with a default cube can trigger this. Sometimes when this happens, even after Blender crashes, the task manager still shows a Blender client running. I highly suspect that this is asset library related because I did a clean install today to solve this issue and everything was perfectly fine until I started installing the asset library paths back in. If the crash doesn't happen right away at start up, then I am safe to work on that file until I try to open it again. **Exact steps for others to reproduce the error** I have years of asset library saved up and potentially hundreds of GB of models and textures within it. So for me to reproduce the error, all I need to do is open Blender and chances are it will crash. Due to this, it is impossible for me to provide a blend file that is usable.

Screenshot 2024-03-20 175247.jpg

173 KiB

blender.crash.txt

176 KiB

Steve-Wang added the

labels 2024-03-21 01:58:38 +01:00

Pratik Borhade commented

2024-03-21 05:39:37 +01:00

Hi, thanks for the report. I think this has been resolved in 4.1 release candidate, can you check: https://builder.blender.org/download/daily/

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-03-21 05:47:52 +01:00

Steve-Wang commented

2024-03-21 16:04:01 +01:00

Hi Pratik,

Thanks for the response. I downloaded 4.1 to test it out, and I loaded in my 4.0 settings. Immediately right after the loading process was complete, I saw my ram climb up slowly. The exact same issue seems to be happening here.

Sorry, accidentally clicked on closed issue. This has been reopened.

Hi Pratik, Thanks for the response. I downloaded 4.1 to test it out, and I loaded in my 4.0 settings. Immediately right after the loading process was complete, I saw my ram climb up slowly. The exact same issue seems to be happening here. Sorry, accidentally clicked on closed issue. This has been reopened.

Screenshot 2024-03-21 075701.jpg

419 KiB

Steve-Wang closed this issue

2024-03-21 16:04:04 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-03-21 16:04:06 +01:00

Steve-Wang reopened this issue

2024-03-21 16:04:17 +01:00

Blender Bot added

and removed

labels 2024-03-21 16:04:19 +01:00

Pratik Borhade commented

2024-03-22 04:21:11 +01:00

Thanks. Just to ensure this is related to asset libraries, can you load factory settings then add asset library paths in preferences?: File > Defaults > Load Factory Settings -> open preferences -> File Paths -> Add asset libraries` (don't close blender during this process, otherwise defaults prefs will be removed)

Thanks. Just to ensure this is related to asset libraries, can you load factory settings then add asset library paths in preferences?: `File > Defaults > Load Factory Settings` -> open preferences -> File Paths -> Add asset libraries` (don't close blender during this process, otherwise defaults prefs will be removed)

Pratik Borhade commented

2024-03-22 04:28:11 +01:00

Large asset libraries will surely utilize good amount of memory. Also see: #111614

We are close to 4.1 release now. To ensure this is not a regression, can you confirm the high memory usage in 3.6 build?: https://builder.blender.org/download/daily/ (sorry for asking to test different versions)

Large asset libraries will surely utilize good amount of memory. Also see: #111614 We are close to 4.1 release now. To ensure this is not a regression, can you confirm the high memory usage in 3.6 build?: https://builder.blender.org/download/daily/ (sorry for asking to test different versions)

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-03-22 04:28:23 +01:00

Steve-Wang commented

2024-03-22 17:49:35 +01:00

I will report back after testing it for a few more days. Interestingly enough, 4.1 is actually very stable today and within 20 tries it only crashed twice.

3.6 still presents this issue for me. I started experiencing this issue when I upgraded from 3.4 to 3.6. Just like 4.0, 3.6 is very easy for me to reproduce this crash.

I will report back after testing it for a few more days. Interestingly enough, 4.1 is actually very stable today and within 20 tries it only crashed twice. 3.6 still presents this issue for me. I started experiencing this issue when I upgraded from 3.4 to 3.6. Just like 4.0, 3.6 is very easy for me to reproduce this crash.

Steve-Wang commented

2024-04-01 20:37:41 +02:00

After using Blender 4.1 for 6+ hours per day for the past week, I can confirm that while it's way more stable than the previous builds, this crash can definitely still happen.

Pratik Borhade commented

2024-04-02 05:40:32 +02:00

Hi, thanks for getting back. Good to know that 4.1 is not crashing that often on your system. But without being able to reproduce locally, fixing and investigating the crash would be difficult.

DId you check factory reset btw (as suggested in last message)?

Hi, thanks for getting back. Good to know that 4.1 is not crashing that often on your system. But without being able to reproduce locally, fixing and investigating the crash would be difficult. DId you check factory reset btw (as suggested in last message)?

Steve-Wang commented

2024-04-02 06:34:57 +02:00

Yes I did, which is why I am ever more sure of the fact that the issue comes from asset browsers. I must admit that I have an abnormally large asset library built up from years of working.

4.1 is already way more stable so I am quite happy about it.

Yes I did, which is why I am ever more sure of the fact that the issue comes from asset browsers. I must admit that I have an abnormally large asset library built up from years of working. 4.1 is already way more stable so I am quite happy about it.

Pratik Borhade commented

2024-04-02 07:19:07 +02:00

I must admit that I have an abnormally large asset library built up from years of working.

Culprit could be a faulty file/object from the asset library.
Not much we can do in such case. One thing you can do is to narrow down the asset library folder by removing files one by one until the crash occurs.

> I must admit that I have an abnormally large asset library built up from years of working. Culprit could be a faulty file/object from the asset library. Not much we can do in such case. One thing you can do is to narrow down the asset library folder by removing files one by one until the crash occurs.

Pratik Borhade commented

2024-04-16 07:30:56 +02:00

Hi, think we can close this if 4.1 is stable.

Pratik Borhade closed this issue

2024-04-16 07:31:00 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-04-16 07:31:02 +02:00