Blender 2.8: Applying more than one material on a mesh object Blender instantly crashes (Build: a246604937 windows64) #59621

Closed
opened 2018-12-19 15:42:10 +01:00 by Chingiz Jumagulov · 26 comments

System Information

Operating system: Windows 10, 64 bit, 16 gb ram ddr3
Graphics card: Nvidia Geforce 1070, 8gb vram

Blender Version

Date: 2018-12-19 08:13
HASH: a246604937
Blender 2.8

Broken:

version: 2.80 (sub 37), branch: blender2.8, commit date: 2018-12-13 01:30, hash: 7d4d9e9dbd, type: Release
build date: 12/12/2018, 18:59

Tested and replicated the bug on these versions:

blender 2.80.0 a246604937 windows64

blender 2.80.0 fd42fe6616 windows64

Short description of error

Upon applying more than one material on a mesh object using materials tab in the properties window will cause instant crash of Blender.
Video of the bug is attached to this message, also I've attached the blend file used in the video.
Also, I've generated two system info txt files, one is generated via Blender and another one is generated by msinfo32 in Windows.

Thank you guys for all your amazing work!

(P.S. Sorry for scary desktop wallpapers in the video, it's a slideshow of thousands of images in the folder Windows decided to grab those during the video...)

Exact steps for others to reproduce the error

BUG_VIDEO.flv

System_info.txt

Bot_001.blend

system-info2.txt

  1. Open blender
  2. Create mesh material in the viewport
  3. Enter edit mode
  4. Choose faces of the mesh
  5. Open Material tab in the properties window
  6. Create two materials and assign them on different faces of a mesh object.
  7. Crash all the time you attempt to do that.
**System Information** Operating system: Windows 10, 64 bit, 16 gb ram ddr3 Graphics card: Nvidia Geforce 1070, 8gb vram **Blender Version** Date: 2018-12-19 08:13 HASH: a2466049376 Blender 2.8 Broken: version: 2.80 (sub 37), branch: blender2.8, commit date: 2018-12-13 01:30, hash: 7d4d9e9dbd3, type: Release build date: 12/12/2018, 18:59 Tested and replicated the bug on these versions: blender 2.80.0 a2466049376 windows64 blender 2.80.0 fd42fe66161 windows64 **Short description of error** Upon applying more than one material on a mesh object using materials tab in the properties window will cause instant crash of Blender. Video of the bug is attached to this message, also I've attached the blend file used in the video. Also, I've generated two system info txt files, one is generated via Blender and another one is generated by msinfo32 in Windows. Thank you guys for all your amazing work! (P.S. Sorry for scary desktop wallpapers in the video, it's a slideshow of thousands of images in the folder Windows decided to grab those during the video...) **Exact steps for others to reproduce the error** [BUG_VIDEO.flv](https://archive.blender.org/developer/F6007150/BUG_VIDEO.flv) [System_info.txt](https://archive.blender.org/developer/F6007138/System_info.txt) [Bot_001.blend](https://archive.blender.org/developer/F6007135/Bot_001.blend) [system-info2.txt](https://archive.blender.org/developer/F6007112/system-info2.txt) 1) Open blender 2) Create mesh material in the viewport 3) Enter edit mode 4) Choose faces of the mesh 5) Open Material tab in the properties window 6) Create two materials and assign them on different faces of a mesh object. 7) Crash all the time you attempt to do that.

Added subscriber: @MeshVoid

Added subscriber: @MeshVoid

Added subscriber: @ZedDB

Added subscriber: @ZedDB

I can not reproduce this issue.

In the off chance that this is a GPU related issue, could you update your nvidia drivers to the latest version? https://www.nvidia.com/Download/index.aspx?lang=en-us

If that doesn't help, could you run blender with "--debug-gpu" and attach the output?
You can also try to run blender with "--debug-gpu-force-workarounds" and see if that helps too.

I can not reproduce this issue. In the off chance that this is a GPU related issue, could you update your nvidia drivers to the latest version? https://www.nvidia.com/Download/index.aspx?lang=en-us If that doesn't help, could you run blender with "--debug-gpu" and attach the output? You can also try to run blender with "--debug-gpu-force-workarounds" and see if that helps too.

Hi! Thank you for your reply! I've done a clean install of the latest Nvidia drivers on my system and rebooted the system. Then tried again and stumbled across the same issue, it crashes upon adding more than one material and assigning it to face of a mesh, or sometimes when you create a new material. I've started blender through cmd line using both "--debug-gpu" and "--debug-gpu-force-workarounds" commands, but it crashed again. I've recorded a video of the crash and also saved the error output from the cmd window into two separate text files.

Debug_GPU_LOG.txt

DEBUG_GPU_WORKAROUNDS_LOG.txt

Bug_report_video_002.flv

Hi! Thank you for your reply! I've done a clean install of the latest Nvidia drivers on my system and rebooted the system. Then tried again and stumbled across the same issue, it crashes upon adding more than one material and assigning it to face of a mesh, or sometimes when you create a new material. I've started blender through cmd line using both "--debug-gpu" and "--debug-gpu-force-workarounds" commands, but it crashed again. I've recorded a video of the crash and also saved the error output from the cmd window into two separate text files. [Debug_GPU_LOG.txt](https://archive.blender.org/developer/F6008430/Debug_GPU_LOG.txt) [DEBUG_GPU_WORKAROUNDS_LOG.txt](https://archive.blender.org/developer/F6008429/DEBUG_GPU_WORKAROUNDS_LOG.txt) [Bug_report_video_002.flv](https://archive.blender.org/developer/F6008428/Bug_report_video_002.flv)
Clément Foucault was assigned by Sebastian Parborg 2018-12-19 18:52:16 +01:00

Added subscriber: @fclem

Added subscriber: @fclem

@fclem don't know if this is your area, but because I can't reproduce this, I'm guessing it is GPU related.

@fclem don't know if this is your area, but because I can't reproduce this, I'm guessing it is GPU related.

That is such a random bug... It works on certain types of geometry in the scene, for example, if I create a new scene with a cube and then try applying materials to it it will work fine. But when I work in that specific scene that I've originally attached and apply materials on certain objects it gives the error always resulting to EXCEPTION_ACCESS_VIOLATION and the same address in the cmd log. I've made another video of the bug, I apply multiple materials on one object successfully, but when I apply multiple materials on other objects it crashes. I've tried also clearing all data from the objects, but it still crashes in the same fashion.

Bug_report_video_003.flv

Debug_gpu_output2.txt

That is such a random bug... It works on certain types of geometry in the scene, for example, if I create a new scene with a cube and then try applying materials to it it will work fine. But when I work in that specific scene that I've originally attached and apply materials on certain objects it gives the error always resulting to EXCEPTION_ACCESS_VIOLATION and the same address in the cmd log. I've made another video of the bug, I apply multiple materials on one object successfully, but when I apply multiple materials on other objects it crashes. I've tried also clearing all data from the objects, but it still crashes in the same fashion. [Bug_report_video_003.flv](https://archive.blender.org/developer/F6008752/Bug_report_video_003.flv) [Debug_gpu_output2.txt](https://archive.blender.org/developer/F6008750/Debug_gpu_output2.txt)

I've created a scene with multiple objects and crazy amount of materials and applied it to different objects, and it works fine. For some reason, the bug appears to be present in that particular blend file, I don't know what is the cause (most probably object refers to a restricted GPU memory address when applying several materials for some reason), I guess I'll just create a new scene and import mesh from that blend file or export mesh and import to a new scene, maybe it will fix the problem.

Screenshot_1.jpg

I've created a scene with multiple objects and crazy amount of materials and applied it to different objects, and it works fine. For some reason, the bug appears to be present in that particular blend file, I don't know what is the cause (most probably object refers to a restricted GPU memory address when applying several materials for some reason), I guess I'll just create a new scene and import mesh from that blend file or export mesh and import to a new scene, maybe it will fix the problem. ![Screenshot_1.jpg](https://archive.blender.org/developer/F6008872/Screenshot_1.jpg)

Hmm, no, it appears to be super random and present basically in all my blender scenes, where I have worked for an extensive period of time editing the mesh... I guess it is GPU related, but I don't know exactly how to fix this =((...

Hmm, no, it appears to be super random and present basically in all my blender scenes, where I have worked for an extensive period of time editing the mesh... I guess it is GPU related, but I don't know exactly how to fix this =((...

Finally! I have gotten to the bottom of this! The problem occurs ONLY with the mesh that has mirror modifier assigned to it!

Exact steps to reproduce the problem:

  1. Open blender, create a new scene
  2. Delete half of the cube, create empty and apply mirror modifier to a cube with an empty as a mirror target
  3. Open Materials tab in properties
  4. Create couple of materials with different colors
  5. Assign different materials to different faces
  6. Crash

Works 100 % of the cases (At least for me)! For now, I just apply mirror modifier before applying materials as a workaround. But my guess is that it is not a GPU issue, as it has been assumed before, It has something to do with the simultaneous work of Materials tab and symmetry modifier (possibly multiple modifiers, I didn't check array and etc) applied to a mesh object!

Here's a video log of the exact steps to replicate the problem:
Bug_report_video_004.flv

**Finally! I have gotten to the bottom of this!** The problem occurs **ONLY with the mesh that has mirror modifier** assigned to it! *Exact steps to reproduce the problem:* 1) Open blender, create a new scene 2) Delete half of the cube, create empty and apply mirror modifier to a cube with an empty as a mirror target 3) Open Materials tab in properties 4) Create couple of materials with different colors 5) Assign different materials to different faces 6) Crash Works 100 % of the cases (At least for me)! For now, I just apply mirror modifier before applying materials as a workaround. But my guess is that it is not a GPU issue, as it has been assumed before, It has something to do with the simultaneous work of Materials tab and symmetry modifier (possibly multiple modifiers, I didn't check array and etc) applied to a mesh object! Here's a video log of the exact steps to replicate the problem: [Bug_report_video_004.flv](https://archive.blender.org/developer/F6009182/Bug_report_video_004.flv)

Nope, still can't reproduce this on my end. :c

Nope, still can't reproduce this on my end. :c

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke

@JacquesLucke could you see if you can reproduce this?

@JacquesLucke could you see if you can reproduce this?

That's strange, =(. I have this bug all the time with mirror modifier. It's also important to change the base color of materials and apply them to different faces, when they are identical in parameters then it won't crash, as soon as you change base color when the mirror modifier is applied it does crash.

UPDATE: No, actually you don't even have to change the color, just have mirror modifier applied so that the mesh is visibly mirrored in the viewport and apply multiple materials of faces and this will result into crashes all the time.
That's super weird O_o

That's strange, =(. I have this bug all the time with mirror modifier. It's also important to change the base color of materials and apply them to different faces, when they are identical in parameters then it won't crash, as soon as you change base color when the mirror modifier is applied it does crash. UPDATE: No, actually you don't even have to change the color, just have mirror modifier applied so that the mesh is visibly mirrored in the viewport and apply multiple materials of faces and this will result into crashes all the time. That's super weird O_o
Member

Unfortunately I'm also not able to reproduce this bug..

Screenshot from 2018-12-20 11-27-54.png

@MeshVoid Do you have access to some other computer where you can test this?

Unfortunately I'm also not able to reproduce this bug.. ![Screenshot from 2018-12-20 11-27-54.png](https://archive.blender.org/developer/F6014974/Screenshot_from_2018-12-20_11-27-54.png) @MeshVoid Do you have access to some other computer where you can test this?

Could you try resetting to factory defaults just in case that help? I doubt it, but it can't hurt to try...

Could you try resetting to factory defaults just in case that help? I doubt it, but it can't hurt to try...

Wow! I was in a doubt it would help, but resetting to factory defaults did help and the bug is gone like it never been there before! That is strange =)).

Wow! I was in a doubt it would help, but resetting to factory defaults did help and the bug is gone like it never been there before! That is strange =)).
Clément Foucault was unassigned by Sebastian Parborg 2018-12-20 17:00:29 +01:00

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Let us know if you ever figure out what made it behave this way. It seems to be settings related or something then.

Let us know if you ever figure out what made it behave this way. It seems to be settings related or something then.

Added subscriber: @catblue44

Added subscriber: @catblue44

I need to fix this bug to finish a project. resetting to factory only fix if you want to start another project.
Some ideas to fix this?

I need to fix this bug to finish a project. resetting to factory only fix if you want to start another project. Some ideas to fix this?

You have to figure out what is causing this by finding what is different from the factory settings.

You have to figure out what is causing this by finding what is different from the factory settings.

It seems to only happen in the eevee rendering mode. I switched to cycles and it works perfectly for the materials tap. Then I went back to eevee and everything is fine.

It seems to only happen in the eevee rendering mode. I switched to cycles and it works perfectly for the materials tap. Then I went back to eevee and everything is fine.

Added subscriber: @Zombie1ted

Added subscriber: @Zombie1ted

Hello everyone and let's dive straight into it. For the sake of having flat rendered material, I turned to workbench and enabled its flat material render. I tried using blender to apply multiple materials on an object but I was beating in the bush. It made every part where the second material is applied invisible. Baffles me.
Here are info about my laptop
Model name: Dell Latitude e6410
GPU: Nvidia NVS 3100M (for notebooks) [total memory: 2438mb, display memory: 459mb, shared memory: 1978mb]
CPU: Intel Core i5 M 560 (4 CPUs of about 2.67Ghz each)
RAM: 4gb (3.86gb usable)
OS: Win 10
Look at the attachment and you will see by yourselves that the little simple test scene is a mess with multiple materials.
{Blender File}

{Pic 1}

{Pic 2}

{Pic 3}

Hello everyone and let's dive straight into it. For the sake of having flat rendered material, I turned to workbench and enabled its flat material render. I tried using blender to apply multiple materials on an object but I was beating in the bush. It made every part where the second material is applied invisible. Baffles me. Here are info about my laptop Model name: Dell Latitude e6410 GPU: Nvidia NVS 3100M (for notebooks) [total memory: 2438mb, display memory: 459mb, shared memory: 1978mb] CPU: Intel Core i5 M 560 (4 CPUs of about 2.67Ghz each) RAM: 4gb (3.86gb usable) OS: Win 10 Look at the attachment and you will see by yourselves that the little simple test scene is a mess with multiple materials. {Blender File} {Pic 1} {Pic 2} {Pic 3}

Hello everyone and let's dive straight into it. For the sake of having flat rendered material, I turned to workbench and enabled its flat material render. I tried using blender to apply multiple materials on an object but I was beating in the bush. It made every part where the second material is applied invisible. Baffles me.
Here are info about my laptop
Model name: Dell Latitude e6410
GPU: Nvidia NVS 3100M (for notebooks) [total memory: 2438mb, display memory: 459mb, shared memory: 1978mb]
CPU: Intel Core i5 M 560 (4 CPUs of about 2.67Ghz each)
RAM: 4gb (3.86gb usable)
OS: Win 10
Look at the attachment and you will see by yourselves that the little simple test scene is a mess with multiple materials.
blender file >> https://drive.google.com/open?id=1xILWbLTWRyVplhQBUQdsiauHlhG99bPc

Pictures
https://drive.google.com/open?id=1NXHm0UGWDJJe_NoBhL6nsLAbcAQddnRR
https://drive.google.com/open?id=19PNNnCpdPbwMcyQAEIv4c8j8xvMKqYya
https://drive.google.com/open?id=1P4D-cL7f6OJ6KKMYpKXfJFNCVZbWI0SV

Hello everyone and let's dive straight into it. For the sake of having flat rendered material, I turned to workbench and enabled its flat material render. I tried using blender to apply multiple materials on an object but I was beating in the bush. It made every part where the second material is applied invisible. Baffles me. Here are info about my laptop Model name: Dell Latitude e6410 GPU: Nvidia NVS 3100M (for notebooks) [total memory: 2438mb, display memory: 459mb, shared memory: 1978mb] CPU: Intel Core i5 M 560 (4 CPUs of about 2.67Ghz each) RAM: 4gb (3.86gb usable) OS: Win 10 Look at the attachment and you will see by yourselves that the little simple test scene is a mess with multiple materials. blender file >> https://drive.google.com/open?id=1xILWbLTWRyVplhQBUQdsiauHlhG99bPc ----------------------------------------------------------------------------------------------------------- Pictures https://drive.google.com/open?id=1NXHm0UGWDJJe_NoBhL6nsLAbcAQddnRR https://drive.google.com/open?id=19PNNnCpdPbwMcyQAEIv4c8j8xvMKqYya https://drive.google.com/open?id=1P4D-cL7f6OJ6KKMYpKXfJFNCVZbWI0SV
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#59621
No description provided.