Alpha version crashes while applying materials using the Blenderkit addon #82742

New Issue

Paolo Cabaleiro · 2020-11-15T18:57:16+01:00

Paolo Cabaleiro commented

2020-11-15 18:57:16 +01:00

System Information
Operating system: Linux-5.8.18-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits
Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-14 21:24, hash: blender/blender@194a57fd63
Worked: 2.90.1 (From Steam)

Addon Information
Name: BlenderKit Online Asset Library (1, 0, 32)
Author: Vilem Duha, Petr Dlouhy

Short description of error
While trying out different materials, a random crash occurred and in the terminal it was shown as Segmentation Fault. I was able to replicate it multiple times (but not always) just by adding materials until it crashed.
Some details:

I am using an Nvidia Optimus, thus, I was running at first using prime-run to use the GPU directly, however, testing without it, still produced the same crash.
I tested with the same file and doing the same steps on Blender 2.90.1, but was unable to force a crash.
There are some missing references, but have been for long, so I dont believe those should have an impact.
I have attached the main scene, and 2 files from where I appended assets.
Multiple crash files from the different times I was able to force a crash are appended; one of those without using prime-run to run Blender. Also, appended you can find the terminal output from some of the crashes.

Exact steps for others to reproduce the error

Enable Blenderkit addon if not enabled already.
Search on Blenderkit for a wall material, and try to apply to the side wall (2nd material slot, currently called Stone wall)
Repeat applying different materials from Blenderkit a few times (in my case sometimes 1, sometimes ~5)

The file has everything hidden but the walls which have multiple material slots for side, front, etc.
Sometimes I was unable to replicate it, so, not totally sure what exactly could be triggering the segmentation fault. Sometimes I tested going into edit mode to apply the material and the crash was there, but other times it had no impact.

If I am missing any information, or further details would help, please let me know, I am more than happy to do so.

Bowling Pin.blend

Bowling Ball Returner.blend

system-info.txt

Bowling Alley8 - 5th Crash - Without prime-run.crash.txt

Bowling Alley8 - 4th Crash.crash.txt

Bowling Alley8 - 3rd Crash.crash.txt

Bowling Alley8 - 2nd Crash.crash.txt

Bowling Alley8.terminal output - Without prime-run.txt

Bowling Alley8.terminal output.txt

Bowling Alley8.blend

Bowling Alley8.crash.txt

**System Information** Operating system: Linux-5.8.18-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits Graphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38 **Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-11-14 21:24, hash: `blender/blender@194a57fd63` Worked: 2.90.1 (From Steam) **Addon Information** Name: BlenderKit Online Asset Library (1, 0, 32) Author: Vilem Duha, Petr Dlouhy **Short description of error** While trying out different materials, a random crash occurred and in the terminal it was shown as Segmentation Fault. I was able to replicate it multiple times (but not always) just by adding materials until it crashed. Some details: - I am using an Nvidia Optimus, thus, I was running at first using `prime-run` to use the GPU directly, however, testing without it, still produced the same crash. - I tested with the same file and doing the same steps on Blender 2.90.1, but was unable to force a crash. - There are some missing references, but have been for long, so I dont believe those should have an impact. - I have attached the main scene, and 2 files from where I appended assets. - Multiple crash files from the different times I was able to force a crash are appended; one of those without using `prime-run` to run Blender. Also, appended you can find the terminal output from some of the crashes. **Exact steps for others to reproduce the error** - Enable Blenderkit addon if not enabled already. - Search on Blenderkit for a wall material, and try to apply to the side wall (2nd material slot, currently called Stone wall) - Repeat applying **different** materials from Blenderkit a few times (in my case sometimes 1, sometimes ~5) The file has everything hidden but the walls which have multiple material slots for side, front, etc. Sometimes I was unable to replicate it, so, not totally sure what exactly could be triggering the segmentation fault. Sometimes I tested going into edit mode to apply the material and the crash was there, but other times it had no impact. If I am missing any information, or further details would help, please let me know, I am more than happy to do so. [Bowling Pin.blend](https://archive.blender.org/developer/F9294347/Bowling_Pin.blend) [Bowling Ball Returner.blend](https://archive.blender.org/developer/F9294346/Bowling_Ball_Returner.blend) [system-info.txt](https://archive.blender.org/developer/F9294345/system-info.txt) [Bowling Alley8 - 5th Crash - Without prime-run.crash.txt](https://archive.blender.org/developer/F9294344/Bowling_Alley8_-_5th_Crash_-_Without_prime-run.crash.txt) [Bowling Alley8 - 4th Crash.crash.txt](https://archive.blender.org/developer/F9294343/Bowling_Alley8_-_4th_Crash.crash.txt) [Bowling Alley8 - 3rd Crash.crash.txt](https://archive.blender.org/developer/F9294342/Bowling_Alley8_-_3rd_Crash.crash.txt) [Bowling Alley8 - 2nd Crash.crash.txt](https://archive.blender.org/developer/F9294341/Bowling_Alley8_-_2nd_Crash.crash.txt) [Bowling Alley8.terminal output - Without prime-run.txt](https://archive.blender.org/developer/F9294340/Bowling_Alley8.terminal_output_-_Without_prime-run.txt) [Bowling Alley8.terminal output.txt](https://archive.blender.org/developer/F9294339/Bowling_Alley8.terminal_output.txt) [Bowling Alley8.blend](https://archive.blender.org/developer/F9294338/Bowling_Alley8.blend) [Bowling Alley8.crash.txt](https://archive.blender.org/developer/F9294337/Bowling_Alley8.crash.txt)

Paolo Cabaleiro commented

2020-11-15 18:57:16 +01:00

Added subscriber: @PaoloCabaleiro

Paolo Cabaleiro commented

2020-11-15 20:30:35 +01:00

After noticing the size of the original file, I created a stripped down version of it, containing only the walls. After that, I ran the same tests as described before, and was able to replicate the crash as well. Feel free to let me know if I should remove the original file as this one should suffice.
Bowling Alley8 - Minimal.blend

After noticing the size of the original file, I created a stripped down version of it, containing only the walls. After that, I ran the same tests as described before, and was able to replicate the crash as well. Feel free to let me know if I should remove the original file as this one should suffice. [Bowling Alley8 - Minimal.blend](https://archive.blender.org/developer/F9295261/Bowling_Alley8_-_Minimal.blend)

Evan Wilson commented

2020-11-16 01:00:10 +01:00

Added subscribers: @VilemDuha, @EAW

Evan Wilson commented

2020-11-16 01:00:10 +01:00

Paging @VilemDuha

Vilem Duha self-assigned this 2020-11-25 10:06:30 +01:00

Vilem Duha commented

2020-11-25 10:06:30 +01:00

Trying to reproduce - was Cycles on during the crashes? or was it in material preview mode?

What BlenderKit does is that it can append plenty of materials faster than usual, so the memory can get filled relatively fast. This will be improved in Blender 2.92 with the introduction of texture resolutions for all texture based assets.

I just tried drag-dropping about 50 materials in the scene, all with 4k, usually 5 at once (each wall for 1) and things worked smoothly, but was on a 2080 Ti. It points in the direction of Cycles+GPU+appending the assets during rendering being switched on.

Trying to reproduce - was Cycles on during the crashes? or was it in material preview mode? What BlenderKit does is that it can append plenty of materials faster than usual, so the memory can get filled relatively fast. This will be improved in Blender 2.92 with the introduction of texture resolutions for all texture based assets. I just tried drag-dropping about 50 materials in the scene, all with 4k, usually 5 at once (each wall for 1) and things worked smoothly, but was on a 2080 Ti. It points in the direction of Cycles+GPU+appending the assets during rendering being switched on.

Paolo Cabaleiro commented

2020-12-08 18:02:20 +01:00

@VilemDuha Apologies for the late reply.

As far as I saw, the crash always happened only on material preview mode; I was unable to reproduce it on render mode on EEVEE, or Cycles.

However, I was able to reproduce the crash even after removing Blenderkit (keeping the materials thou). I am attaching two files I was able to capture using gdb with further information that I hope might be useful.

Extra Crash Info

Extra Crash Info 2

@VilemDuha Apologies for the late reply. As far as I saw, the crash always happened only on material preview mode; I was unable to reproduce it on render mode on EEVEE, or Cycles. However, I was able to reproduce the crash even after removing Blenderkit (keeping the materials thou). I am attaching two files I was able to capture using gdb with further information that I hope might be useful. [Extra Crash Info](https://archive.blender.org/developer/F9494455/Extra_Crash_Info) [Extra Crash Info 2](https://archive.blender.org/developer/F9494456/Extra_Crash_Info_2)

Aaron Carlisle commented

2021-12-08 19:40:13 +01:00

Added subscriber: @Blendify