Regression: Crashes when uses preview or final render modes #112678

Open
opened 2023-09-21 17:15:30 +02:00 by Carlos-Clarivan · 13 comments

System Information
Operating system: Mac Os Monterey 12.6.1
Graphics card: AMD Radeon R9 M380 2 GB

Blender Version
Broken: blender 3.6.2
Worked: Blender 3.4.1

Short description of error
Blender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.

Exact steps for others to reproduce the error
Simply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.

**System Information** Operating system: Mac Os Monterey 12.6.1 Graphics card: AMD Radeon R9 M380 2 GB **Blender Version** Broken: blender 3.6.2 Worked: Blender 3.4.1 **Short description of error** Blender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements. **Exact steps for others to reproduce the error** Simply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.
Carlos-Clarivan added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-09-21 17:15:30 +02:00
Iliya Katushenock added the
Platform
macOS
label 2023-09-21 17:19:19 +02:00
Iliya Katushenock changed title from Blender 3.6.2 crashes on MacOS when uses preview or final render modes to Blender 3.6.2 crashes when uses preview or final render modes 2023-09-21 17:19:26 +02:00
Iliya Katushenock changed title from Blender 3.6.2 crashes when uses preview or final render modes to Regression: Blender 3.6.2 crashes when uses preview or final render modes 2023-09-21 17:19:38 +02:00
Iliya Katushenock changed title from Regression: Blender 3.6.2 crashes when uses preview or final render modes to Regression: Crashes when uses preview or final render modes 2023-09-21 17:19:48 +02:00
Iliya Katushenock added this to the 3.6 LTS milestone 2023-09-21 17:19:52 +02:00
Member

Hi, thanks for the report. Please share affected .blend file to verify and investigate the crash.

Crashed Thread: 0 libembree4.dylib 0x113a29188 embree::TriangleMesh::setBuffer(RTCBufferType, unsigned int, RTCFormat, embree::Ref const&, unsigned long, unsigned long, unsigned int) + 216\ 1 libembree4.dylib 0x1139dafb5 rtcSetSharedGeometryBuffer + 261\ 2 Blender 0x1031c1143 ccl::BVHEmbree::set_tri_vertex_buffer(RTCGeometryTy*, ccl::Mesh const*, bool) + 499\ 3 Blender 0x1031c0a0e ccl::BVHEmbree::add_triangles(ccl::Object const*, ccl::Mesh const*, int) + 318\ 4 Blender 0x1031c026e ccl::BVHEmbree::build(ccl::Progress&, ccl::Stats*, RTCDeviceTy*, bool) + 398\ 5 Blender 0x1031ce8ec ccl::CPUDevice::build_bvh(ccl::BVH*, ccl::Progress&, bool) + 108\ 6 Blender 0x1037a2bd9 ccl::GeometryManager::device_update_bvh(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 665\ 7 Blender 0x10379ca8e ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 5614\ 8 Blender 0x10384b40d ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1757\ 9 Blender 0x10384d043 ccl::Scene::update(ccl::Progress&) + 163\ 10 Blender 0x103956e2e ccl::Session::run_update_for_next_iteration() + 1390\ 11 Blender 0x1039563c4 ccl::Session::run_main_render_loop() + 100\ 12 Blender 0x103957433 ccl::Session::thread_render() + 259\ 13 Blender 0x103954f38 ccl::Session::thread_run() + 168\ 14 Blender 0x1061cd4a3 ccl:🧵:run(void*) + 19\ 15 libsystem_pthread.dylib 0x7ff804afa4e1 _pthread_start + 125\ 16 libsystem_pthread.dylib 0x7ff804af5f6b thread_start + 15\
Hi, thanks for the report. Please share affected .blend file to verify and investigate the crash. <details> <summary> Crashed Thread: </summary> 0 libembree4.dylib 0x113a29188 embree::TriangleMesh::setBuffer(RTCBufferType, unsigned int, RTCFormat, embree::Ref<embree::Buffer> const&, unsigned long, unsigned long, unsigned int) + 216\ 1 libembree4.dylib 0x1139dafb5 rtcSetSharedGeometryBuffer + 261\ 2 Blender 0x1031c1143 ccl::BVHEmbree::set_tri_vertex_buffer(RTCGeometryTy*, ccl::Mesh const*, bool) + 499\ 3 Blender 0x1031c0a0e ccl::BVHEmbree::add_triangles(ccl::Object const*, ccl::Mesh const*, int) + 318\ 4 Blender 0x1031c026e ccl::BVHEmbree::build(ccl::Progress&, ccl::Stats*, RTCDeviceTy*, bool) + 398\ 5 Blender 0x1031ce8ec ccl::CPUDevice::build_bvh(ccl::BVH*, ccl::Progress&, bool) + 108\ 6 Blender 0x1037a2bd9 ccl::GeometryManager::device_update_bvh(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 665\ 7 Blender 0x10379ca8e ccl::GeometryManager::device_update(ccl::Device*, ccl::DeviceScene*, ccl::Scene*, ccl::Progress&) + 5614\ 8 Blender 0x10384b40d ccl::Scene::device_update(ccl::Device*, ccl::Progress&) + 1757\ 9 Blender 0x10384d043 ccl::Scene::update(ccl::Progress&) + 163\ 10 Blender 0x103956e2e ccl::Session::run_update_for_next_iteration() + 1390\ 11 Blender 0x1039563c4 ccl::Session::run_main_render_loop() + 100\ 12 Blender 0x103957433 ccl::Session::thread_render() + 259\ 13 Blender 0x103954f38 ccl::Session::thread_run() + 168\ 14 Blender 0x1061cd4a3 ccl::thread::run(void*) + 19\ 15 libsystem_pthread.dylib 0x7ff804afa4e1 _pthread_start + 125\ 16 libsystem_pthread.dylib 0x7ff804af5f6b thread_start + 15\ </details>
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-09-22 06:01:41 +02:00

Sorry, I can't do that. it's is a 4.8 million polygon model, very complex and with many separated objects linked to it. But it is not the model, Blender 3.4.1 works perfect with it. Never crashes. I tried to reproduce the fail in models with less polygons and with no linked elements attached, and it is not easy. In simple models blender 3.6.2 seems to work fine. But in complex models, the application always crashes, sometimes at the moment you press F12 even without having used the render preview mode. I attached for you a new crash report referred to another complex model with linked objects too.

Sorry, I can't do that. it's is a 4.8 million polygon model, very complex and with many separated objects linked to it. But it is not the model, Blender 3.4.1 works perfect with it. Never crashes. I tried to reproduce the fail in models with less polygons and with no linked elements attached, and it is not easy. In simple models blender 3.6.2 seems to work fine. But in complex models, the application always crashes, sometimes at the moment you press F12 even without having used the render preview mode. I attached for you a new crash report referred to another complex model with linked objects too.
Member

Call stack in crashed thread is different this time. Both crash seems unrelated to each other.

Without example .blend file, we won't be able to investigate the crash further.

Crashed Thread

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 Blender 0x10ed7ce8d ghash_buckets_resize + 141
1 Blender 0x10ed7d816 BLI_ghash_ensure_p + 278
2 Blender 0x107847cb9 drw_duplidata_load + 185
3 Blender 0x107846b57 DRW_draw_render_loop_ex + 1095
4 Blender 0x10871a080 view3d_main_region_draw + 208
5 Blender 0x107c57c01 ED_region_do_draw + 337
6 Blender 0x10768d581 wm_draw_update + 1761
7 Blender 0x107689910 WM_main + 48
8 Blender 0x106e79f9e main + 878
9 dyld 0x11ae3652e start + 462\

Call stack in crashed thread is different this time. Both crash seems unrelated to each other. Without example .blend file, we won't be able to investigate the crash further. <details> <summary> Crashed Thread </summary> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread\ 0 Blender 0x10ed7ce8d ghash_buckets_resize + 141\ 1 Blender 0x10ed7d816 BLI_ghash_ensure_p + 278\ 2 Blender 0x107847cb9 drw_duplidata_load + 185\ 3 Blender 0x107846b57 DRW_draw_render_loop_ex + 1095\ 4 Blender 0x10871a080 view3d_main_region_draw + 208\ 5 Blender 0x107c57c01 ED_region_do_draw + 337\ 6 Blender 0x10768d581 wm_draw_update + 1761\ 7 Blender 0x107689910 WM_main + 48\ 8 Blender 0x106e79f9e main + 878\ 9 dyld 0x11ae3652e start + 462\ </details>

I tried with several simpler files and with the new blender 3.6.4 and the problem is repeated over and over again. When working with files with few polygons, the problem is difficult to reproduce. But with heavier objects, it always happens. To this, just do several successive render previews, then you have to perform a final rendering two or three times at low resolution (1980 px). Immediately you have to make a new render preview and it is usually there when Blender closes.

I'm sending you the report (see the attachment) and also the smallest file which I managed to reproduced the problem easily.

You can download the file here:

https://www.dropbox.com/scl/fi/bkk48xs222cs46zzmclvw/FAFT-Test.blend?rlkey=r4p1521vz86bd63zxw56m73mr&dl=0

I tried with several simpler files and with the new blender 3.6.4 and the problem is repeated over and over again. When working with files with few polygons, the problem is difficult to reproduce. But with heavier objects, it always happens. To this, just do several successive render previews, then you have to perform a final rendering two or three times at low resolution (1980 px). Immediately you have to make a new render preview and it is usually there when Blender closes. I'm sending you the report (see the attachment) and also the smallest file which I managed to reproduced the problem easily. You can download the file here: https://www.dropbox.com/scl/fi/bkk48xs222cs46zzmclvw/FAFT-Test.blend?rlkey=r4p1521vz86bd63zxw56m73mr&dl=0

I've been doing more tests and the problem also occurs not only when you move from the final render to the preview render, but also when you make a final render and then try to open the "Shader" tab.

I've been doing more tests and the problem also occurs not only when you move from the final render to the preview render, but also when you make a final render and then try to open the "Shader" tab.
Pratik Borhade added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2023-10-03 13:07:59 +02:00
Member

Function calls in every crash-log are different. So reason is likely to be different for every case.
In recent file has noted metal specific function calls. In which render engine you're observing crash? (cycles?)

Function calls in every crash-log are different. So reason is likely to be different for every case. In recent file has noted metal specific function calls. In which render engine you're observing crash? (cycles?)
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-10-05 12:18:17 +02:00

No, I do not use Eeve. I only use cycles in CPU mode because my computer does not support GPUs. What I have found is that the issue does not happen when I create a new file in Blender 3.6.4 and render it. But perhaps this is only true for very simple files because I have only so far used Blender 3.6.4 to create models with a few polygons. In any case, it does not appear that the files are the issue. It never occurs with Blender 3.4.1. I am currently modeling in Blender 3.6.4 (which I can do without problems using the most recent add-ons), but I am doing my final renders in Blender 3.4.1. And Blender 3.4.1 never fails.

No, I do not use Eeve. I only use cycles in CPU mode because my computer does not support GPUs. What I have found is that the issue does not happen when I create a new file in Blender 3.6.4 and render it. But perhaps this is only true for very simple files because I have only so far used Blender 3.6.4 to create models with a few polygons. In any case, it does not appear that the files are the issue. It never occurs with Blender 3.4.1. I am currently modeling in Blender 3.6.4 (which I can do without problems using the most recent add-ons), but I am doing my final renders in Blender 3.4.1. And Blender 3.4.1 never fails.

I started a new test from scratch, and for a while everything went smoothly as I rendered in final and preview modes without any issues. However, as I was rendering a preview, the program abruptly crashed. This new file I tested is not particularly large because it only has 277 000 polygons. The crash report and the entire folder file with all the textures are attached.

Folder link:

https://www.dropbox.com/scl/fo/7qgva55p3veom6q3mu1c6/h?rlkey=e9y8v8jlm3z950xc7juqr6lso&dl=0

I started a new test from scratch, and for a while everything went smoothly as I rendered in final and preview modes without any issues. However, as I was rendering a preview, the program abruptly crashed. This new file I tested is not particularly large because it only has 277 000 polygons. The crash report and the entire folder file with all the textures are attached. Folder link: https://www.dropbox.com/scl/fo/7qgva55p3veom6q3mu1c6/h?rlkey=e9y8v8jlm3z950xc7juqr6lso&dl=0
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-10-07 17:58:47 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-10-07 17:58:54 +02:00
Member

@Carlos-Clarivan hi, can you reshare the .blend file? I'll find someone who can test on similar setup

@Carlos-Clarivan hi, can you reshare the .blend file? I'll find someone who can test on similar setup
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-18 05:02:26 +01:00
Member
@Carlos-Clarivan ^

I appreciate your efforts. The original file as well as the very early crash reports are available here. https://www.dropbox.com/scl/fo/gdklbnt3awhutdunfxqkz/h?rlkey=c99hkz2xz896tzb7yb4woqmzg&dl=0

I appreciate your efforts. The original file as well as the very early crash reports are available here. https://www.dropbox.com/scl/fo/gdklbnt3awhutdunfxqkz/h?rlkey=c99hkz2xz896tzb7yb4woqmzg&dl=0
Member

Thanks, is crash still relevant in 4.1 build?: https://builder.blender.org/download/daily/

@Alaska hi, can you replicate the crash?

Thanks, is crash still relevant in 4.1 build?: https://builder.blender.org/download/daily/ @Alaska hi, can you replicate the crash?
Member

Using Blender 3.6.2 (what the. user was using in the original report), with the blend file from the most recent dropbox link, I could not reproduce the crash.

The steps I tried were:

  1. Go into Cycles rendered viewport mode, then go out of it, and repeat 10 or some times, then do a final render.
  2. Have 6 active Cycles viewport renders active and start a final render.
  3. Start a final render, and while the render is running switch to the Shading tab where I have two 3D viewports which I keep switching between solid, wireframe, material preview, and Cycles rendered view.

And I tried both of these tests with the Metal and OpenGL Blender graphics API.

I will note that the textures are missing from this file, so it may have a impact on things.


As @PratikPB2123 has pointed out, the cause for crashing seems to keep changing. In one crash log Embree was the cause for crashing (Embree being the BVH and intersection system used by Cycles on the CPU). In another, there was a crash when drawing the GUI.

I suspect this issue is specific to certain generations of Intel CPU + AMD GPU macs, if it's not caused by failing hardware, or a buggy addon of some kind.

@Carlos-Clarivan switching to the OpenGL backend for Blender may help you. To do this, open Blender 3.6.X or certain older versions, then:

  1. Select from the top of Blender Edit -> Preferences
  2. From the left select the System tab.
  3. In the middle expand the GPU Backend menu and change it to OpenGL if it isn't there already.
  4. Select the three little lines down in the bottom left of the preferences window and select Save Preferences
  5. Close and re-open this version of Blender and test again.

This may help with some of the Metal related crashes you seemed to be getting.


System Information
Operating system: macOS-14.2.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2
Blender version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a

Using Blender 3.6.2 (what the. user was using in the original report), with the blend file from the most recent dropbox link, I could not reproduce the crash. The steps I tried were: 1. Go into Cycles rendered viewport mode, then go out of it, and repeat 10 or some times, then do a final render. 2. Have 6 active Cycles viewport renders active and start a final render. 3. Start a final render, and while the render is running switch to the `Shading tab` where I have two 3D viewports which I keep switching between solid, wireframe, material preview, and Cycles rendered view. And I tried both of these tests with the Metal and OpenGL Blender graphics API. I will note that the textures are missing from this file, so it may have a impact on things. --- As @PratikPB2123 has pointed out, the cause for crashing seems to keep changing. In one crash log Embree was the cause for crashing (Embree being the BVH and intersection system used by Cycles on the CPU). In another, there was a crash when drawing the GUI. I suspect this issue is specific to certain generations of Intel CPU + AMD GPU macs, if it's not caused by failing hardware, or a buggy addon of some kind. @Carlos-Clarivan switching to the OpenGL backend for Blender may help you. To do this, open Blender 3.6.X or certain older versions, then: 1. Select from the top of Blender `Edit -> Preferences` 2. From the left select the `System` tab. 3. In the middle expand the `GPU Backend` menu and change it to OpenGL if it isn't there already. 4. Select the three little lines down in the bottom left of the preferences window and select `Save Preferences` 5. Close and re-open this version of Blender and test again. This may help with some of the Metal related crashes you seemed to be getting. --- **System Information** Operating system: macOS-14.2.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 Blender version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: `e53e55951e7a`
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
3 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#112678
No description provided.