Blender 3.5.1 keeps crashing on occasion #107941

New Issue

Lisa-Wiechert · 2023-05-15T14:40:04+02:00

Lisa-Wiechert commented

2023-05-15 14:40:04 +02:00

First-time contributor

System Information
Operating system: Mac OS Ventura 13.3.1 (a) (22E772610a)
Graphics card: Apple M1 Ultra (64-Core GPU)

Blender Version
Broken: Version 3.5.1 (3.5.1 2023-04-25)
Worked: N/A

Short description of error
Blender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error.

Exact steps for others to reproduce the error

Download and open the demo-file Blender 3.4 – “Charge” Open Movie from https://www.blender.org/download/demo-files/
Change the engine from Eevee to Cycles GPU
Set "Viewport Shading" to "Rendered" - nothing happens
Go back to Solid View - blender freezes

The same happens with some of my heavy(ish) project in 3.6.0 beta

In 3.5.1 the same project responds in render view as it should be.

When I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)
I manage to reopen the project after a few crashes.

I hope it helps!

**System Information** Operating system: Mac OS Ventura 13.3.1 (a) (22E772610a) Graphics card: Apple M1 Ultra (64-Core GPU) **Blender Version** Broken: Version 3.5.1 (3.5.1 2023-04-25) Worked: N/A **Short description of error** Blender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error. <video src="/attachments/588fcec3-6239-4b3c-8dd7-fdfb545849dc" controls></video> **Exact steps for others to reproduce the error** - Download and open the demo-file `Blender 3.4 – “Charge” Open Movie` from https://www.blender.org/download/demo-files/ - Change the engine from Eevee to Cycles GPU - Set "Viewport Shading" to "Rendered" - nothing happens - Go back to Solid View - blender freezes The same happens with some of my heavy(ish) project in 3.6.0 beta In 3.5.1 the same project responds in render view as it should be. When I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached) I manage to reopen the project after a few crashes. I hope it helps! ![3.6.0 crash after trying to reopen test file.rtf](attachments/9719bec7-746c-4b39-b36d-1880be6688f4)

Lisa-Wiechert added the

labels 2023-05-15 14:40:05 +02:00

Michael Parkin-White commented

2023-05-15 15:13:12 +02:00

First-time contributor

Thanks for the report!

Would you be able to provide the simple test file you were using? It's possible that the exact window setup and which rendering engines you are using could inform what the cause of the problem is.

Would you also be able to verify whether this happens with both OpenGL and Metal backends, or just Metal? (User preferences/System/GPU backend).

As this sounds like it is related to saving, it would also be great to know whether the issue still happens with autosave disabled, and with File Preview Type set to None?

This could possibly be related to the render preview image rendering during saving with the Metal backend, but answers to the above questions would help narrow this down.

I'l also attempt to reproduce locally with a similar test.
Thanks!

Thanks for the report! Would you be able to provide the simple test file you were using? It's possible that the exact window setup and which rendering engines you are using could inform what the cause of the problem is. Would you also be able to verify whether this happens with both OpenGL and Metal backends, or just Metal? (User preferences/System/GPU backend). As this sounds like it is related to saving, it would also be great to know whether the issue still happens with `autosave` disabled, and with `File Preview Type` set to None? This could possibly be related to the render preview image rendering during saving with the Metal backend, but answers to the above questions would help narrow this down. I'l also attempt to reproduce locally with a similar test. Thanks!

Lisa-Wiechert commented

2023-05-15 16:48:36 +02:00

First-time contributor

I haven't tweaked any of the settings since installing, and I also didn't save or import the settings from the PC version of blender, although I could still go back and do that, because the old machine is still around.

Anyways, the GPU backend is set to Metal. Currently auto save is enabled, but that's likely by default. I can uncheck that box and see if the problem reoccurs. Also, I am always using Cycles, never Eevee, maybe that's also of importance. The one thing that might be to blame as well is a free differential growth add-on I installed recently (https://github.com/inca/blender-differential-growth/releases/tag/2-1-1). That is an add-on I had not installed on the Windows machine.

I should add that I've only been using Blender for a year, and while I am quite confident with modeling, (basic) shading, lighting and rendering stills (for product shots and whatnot), I still consider myself a novice. I still got a LOT of ground to cover, but seeing as 3D only accounts for 1/4 of my work, it'll take a bit I'm guessing. Therefore all and any help is appreciated :)

I have attached the last two projects where it happened. The larger one crashed only once, and never again after, but I also made sure to manually save more than I normally do. I don't know how much the smaller file can reveal, because when it crashed and blender reopened it basically had all the elements of a fresh scene, except the cube.

I haven't tweaked any of the settings since installing, and I also didn't save or import the settings from the PC version of blender, although I could still go back and do that, because the old machine is still around. Anyways, the GPU backend is set to Metal. Currently auto save is enabled, but that's likely by default. I can uncheck that box and see if the problem reoccurs. Also, I am always using Cycles, never Eevee, maybe that's also of importance. The one thing that might be to blame as well is a free differential growth add-on I installed recently (https://github.com/inca/blender-differential-growth/releases/tag/2-1-1). That is an add-on I had not installed on the Windows machine. I should add that I've only been using Blender for a year, and while I am quite confident with modeling, (basic) shading, lighting and rendering stills (for product shots and whatnot), I still consider myself a novice. I still got a LOT of ground to cover, but seeing as 3D only accounts for 1/4 of my work, it'll take a bit I'm guessing. Therefore all and any help is appreciated :) I have attached the last two projects where it happened. The larger one crashed only once, and never again after, but I also made sure to manually save more than I normally do. I don't know how much the smaller file can reveal, because when it crashed and blender reopened it basically had all the elements of a fresh scene, except the cube.

FathersDay2023.blend

955 KiB

MothersDay2023.blend

39 MiB

Michael Parkin-White commented

2023-05-15 17:01:19 +02:00

First-time contributor

Thank you for all of the info, that's really helpful!
This should be enough to go off of, will see if I can reproduce the issue locally

Thank you for all of the info, that's really helpful! This should be enough to go off of, will see if I can reproduce the issue locally

👍 1

Germano Cavalcante commented

2023-05-16 16:55:00 +02:00

Next time you experience a crash, please copy and attach the text from the crash report to help us diagnose and troubleshoot the issue.

The crash report typically contains valuable information about the error that occurred.

Unfortunately this report can't be triaged as a complete bug report.

For the development team to be able to help, there needs to be either reproducible steps (start blender, press this, then that and crash) or at least a known regression (Blender version X worked, but not version Y).

Many bugs are fixed between the official releases. Please try the latest development snapshot of blender: https://builder.blender.org/download

Next time you experience a crash, please copy and attach the text from the crash report to help us diagnose and troubleshoot the issue. The crash report typically contains valuable information about the error that occurred. Unfortunately this report can't be triaged as a complete bug report. For the development team to be able to help, there needs to be either reproducible steps (start blender, press this, then that and crash) or at least a known regression (Blender version X worked, but not version Y). Many bugs are fixed between the official releases. Please try the latest development snapshot of blender: https://builder.blender.org/download

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-05-16 16:55:10 +02:00

Lisa-Wiechert commented

2023-05-17 08:45:50 +02:00

First-time contributor

I found both crash reports in the Console App. I don't even remember getting a pop up message offering access to a report, but maybe I simply missed it. Anyways, I attached the files to this message; hopefully that'll help shine a light on it.

Oh, and I just remembered also that only since working on the Mac, Blender has frozen up on me in relatively simple files (or in files that never froze on the PC before), and I had to force quit the application. That has happened maybe three times. Another curious thing is that, on occasion, just hovering and moving the mouse over the main window of Blender (in the view port as well as the outliner), the application flickers. At first I thought it was only happening in the shading view port, but it happens regardless of what mode the view port Blender is in when it does happen. It flickers basically every time I move the mouse.
It doesn't happen a lo though, it's not like it's a constant thing. But it's something that has never happened on the PC.

I found both crash reports in the Console App. I don't even remember getting a pop up message offering access to a report, but maybe I simply missed it. Anyways, I attached the files to this message; hopefully that'll help shine a light on it. Oh, and I just remembered also that only since working on the Mac, Blender has frozen up on me in relatively simple files (or in files that never froze on the PC before), and I had to force quit the application. That has happened maybe three times. Another curious thing is that, on occasion, just hovering and moving the mouse over the main window of Blender (in the view port as well as the outliner), the application flickers. At first I thought it was only happening in the shading view port, but it happens regardless of what mode the view port Blender is in when it does happen. It flickers basically every time I move the mouse. It doesn't happen a lo though, it's not like it's a constant thing. But it's something that has never happened on the PC.

Blender_Crash_05-11-23.txt

184 KiB

Blender_Crash_05-15-23.txt

179 KiB

Michael Parkin-White commented

2023-05-17 08:59:24 +02:00

First-time contributor

Thanks, these are super helpful! This should help significantly narrow down the problem, looks like in both instances, it is related to multithreading, and likely to do with memory allocation in Metal when being called from a secondary thread.

Will investigate the underlying cause.

Thanks, these are super helpful! This should help significantly narrow down the problem, looks like in both instances, it is related to multithreading, and likely to do with memory allocation in Metal when being called from a secondary thread. Will investigate the underlying cause.

👍 1

Lisa-Wiechert commented

2023-05-24 14:27:45 +02:00

First-time contributor

It happened again, yay... I've been working on various files today, no idea what prompted this crash in particular.

This time it happened right after Blender froze up on me and had to be force quit. I was trying to sculpt, then change angles, the object froze in the view finder, but I was still able to move around the view finder, just with this ghost-like image at the center. I tried taking a screenshot, but the Mac wouldn't let me. Then the beach ball of death appeared, I waited for five minutes, and when nothing happened I force quit the program. No crash report here.

Then I tried proportional editing, which worked. Then I tweaked the lights and wanted to do more proportional editing. As I was in the process of selecting the vertices in question, Blender crashed. Everything was saved up until the point before I tweaked the lights. I have attached both the crash report and the file in question, which is in the state I found it right after the crash.

PS: yes, I know the texture is wrong... I reused this body from a different project where it had a material applied to it instead of a texture. But I only need the front view right now (but... right now), so I will recreate the wrapping later from scratch and figure this out ¯_ (ツ)_/¯

It happened again, yay... I've been working on various files today, no idea what prompted this crash in particular. This time it happened right after Blender froze up on me and had to be force quit. I was trying to sculpt, then change angles, the object froze in the view finder, but I was still able to move around the view finder, just with this ghost-like image at the center. I tried taking a screenshot, but the Mac wouldn't let me. Then the beach ball of death appeared, I waited for five minutes, and when nothing happened I force quit the program. No crash report here. Then I tried proportional editing, which worked. Then I tweaked the lights and wanted to do more proportional editing. As I was in the process of selecting the vertices in question, Blender crashed. Everything was saved up until the point before I tweaked the lights. I have attached both the crash report and the file in question, which is in the state I found it right after the crash. PS: yes, I know the texture is wrong... I reused this body from a different project where it had a material applied to it instead of a texture. But I only need the front view right now (but... _right now_), so I will recreate the wrapping later from scratch and figure this out ¯\_ (ツ)_/¯

OK_OatmealCookie_ProductImage_Render.blend

2.4 MiB

Blender_Crash_05-24-23.txt

209 KiB

Henris commented

2023-06-02 10:27:31 +02:00

First-time contributor

I want to second that, I started to experience "random" crashes on my M1 pro and reading Michael Parkin-White comments about Metal and Memory it makes sense. My scene is kinda large and takes 7-9 GB while rendering. After Rendering in Cycles I can't go to Dev / shaded view. Blender is not crashed, but it's frozen. I still can perform save shortcut and looks like it saving / working, but interface is frozen. I get same issues while jumping from blender to substance painter and back - this is not always, but happens. It feels like some choke in memory management. P.S. I started to experience this more after 3.5 update, before I was working in 3.1

Michael Parkin-White commented

2023-06-02 10:57:22 +02:00

First-time contributor

Thank you very much for the detailed information @Lisa-Wiechert !
Are you still running 3.5.0/3.5.1 when these issues occur? A number of patches have landed (or are soon due to land) in the current 3.6.0 Beta. While the exact issue is hard to pin down due to its inconsistency, there were a number of more consistently reproducible issues which now have patches.

@Henris Thank you for the information, a few new fixes have landed which may address this. The latest 3.6.0 Beta has a new patch for improved memory management in the new Metal backend, which reduces system resource pressure if memory increases above a reasonable limit.

The UI freezing issue is usually caused by a GPU timeout having triggered at some point in time, resulting in the UI no longer updating due to rendering commands being skipped after the timeout. A few of these issues had been root-caused and a fix has also landed in the 3.6.0 beta branch.

It would certainly be a great help to know if these issues are still occurring in the latest 3.6.0 Beta build:
https://builder.blender.org/download/daily/

Though I will continue to investigate the problem and test out the scene attached. Although the specific crash log from @Lisa-Wiechert appears to point to an issue which may be outside of the GPU module itself, as this appears to be a Seg fault caused inside the subdivision code:

Thread 24 Crashed:
0   Blender                       	       0x102a660d8 subdiv_mesh_ensure_vertex_interpolation(SubdivMeshContext*, SubdivMeshTLS*, MPoly const*, int) + 64
1   Blender                       	       0x102a656c0 subdiv_mesh_vertex_inner(SubdivForeachContext const*, void*, int, float, float, int, int, int) + 116
2   Blender                       	       0x102a61ae8 subdiv_foreach_task(void*, int, TaskParallelTLS const*) + 268
3   Blender                       	       0x1094ea438 void tbb::interface9::internal::dynamic_grainsize_mode<tbb::interface9::internal::adaptive_mode<tbb::interface9::internal::auto_partition_type>>::work_balance<tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>, tbb::blocked_range<int>>(tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>&, tbb::blocked_range<int>&) + 592
4   Blender                       	       0x1094ea088 void tbb::interface9::internal::partition_type_base<tbb::interface9::internal::auto_partition_type>::execute<tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>, tbb::blocked_range<int>>(tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>&, tbb::blocked_range<int>&) + 152
5   Blender                       	       0x1094e9fdc tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>::execute() + 112
6   libtbb.dylib                  	       0x111eac718 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 440
7   libtbb.dylib                  	       0x111eabdb4 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 188
8   libtbb.dylib                  	       0x111e97da0 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252
9   libtbb.dylib                  	       0x111ea2bc0 tbb::internal::market::process(rml::job&) + 40
10  libtbb.dylib                  	       0x111ea5b2c tbb::internal::rml::private_worker::run() + 284
11  libtbb.dylib                  	       0x111ea5a04 tbb::internal::rml::private_worker::thread_routine(void*) + 12
12  libsystem_pthread.dylib       	       0x1a2f87fa8 _pthread_start + 148
13  libsystem_pthread.dylib       	       0x1a2f82da0 thread_start + 8

Thank you very much for the detailed information @Lisa-Wiechert ! Are you still running 3.5.0/3.5.1 when these issues occur? A number of patches have landed (or are soon due to land) in the current 3.6.0 Beta. While the exact issue is hard to pin down due to its inconsistency, there were a number of more consistently reproducible issues which now have patches. @Henris Thank you for the information, a few new fixes have landed which may address this. The latest 3.6.0 Beta has a new patch for improved memory management in the new Metal backend, which reduces system resource pressure if memory increases above a reasonable limit. The UI freezing issue is usually caused by a GPU timeout having triggered at some point in time, resulting in the UI no longer updating due to rendering commands being skipped after the timeout. A few of these issues had been root-caused and a fix has also landed in the 3.6.0 beta branch. It would certainly be a great help to know if these issues are still occurring in the latest 3.6.0 Beta build: https://builder.blender.org/download/daily/ Though I will continue to investigate the problem and test out the scene attached. Although the specific crash log from @Lisa-Wiechert appears to point to an issue which may be outside of the GPU module itself, as this appears to be a Seg fault caused inside the subdivision code: ``` Thread 24 Crashed: 0 Blender 0x102a660d8 subdiv_mesh_ensure_vertex_interpolation(SubdivMeshContext*, SubdivMeshTLS*, MPoly const*, int) + 64 1 Blender 0x102a656c0 subdiv_mesh_vertex_inner(SubdivForeachContext const*, void*, int, float, float, int, int, int) + 116 2 Blender 0x102a61ae8 subdiv_foreach_task(void*, int, TaskParallelTLS const*) + 268 3 Blender 0x1094ea438 void tbb::interface9::internal::dynamic_grainsize_mode<tbb::interface9::internal::adaptive_mode<tbb::interface9::internal::auto_partition_type>>::work_balance<tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>, tbb::blocked_range<int>>(tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>&, tbb::blocked_range<int>&) + 592 4 Blender 0x1094ea088 void tbb::interface9::internal::partition_type_base<tbb::interface9::internal::auto_partition_type>::execute<tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>, tbb::blocked_range<int>>(tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>&, tbb::blocked_range<int>&) + 152 5 Blender 0x1094e9fdc tbb::interface9::internal::start_for<tbb::blocked_range<int>, RangeTask, tbb::auto_partitioner const>::execute() + 112 6 libtbb.dylib 0x111eac718 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 440 7 libtbb.dylib 0x111eabdb4 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 188 8 libtbb.dylib 0x111e97da0 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252 9 libtbb.dylib 0x111ea2bc0 tbb::internal::market::process(rml::job&) + 40 10 libtbb.dylib 0x111ea5b2c tbb::internal::rml::private_worker::run() + 284 11 libtbb.dylib 0x111ea5a04 tbb::internal::rml::private_worker::thread_routine(void*) + 12 12 libsystem_pthread.dylib 0x1a2f87fa8 _pthread_start + 148 13 libsystem_pthread.dylib 0x1a2f82da0 thread_start + 8 ```

👍 2

Panos Pagonis commented

2023-06-03 23:12:56 +02:00

First-time contributor

Hello

I am not sure if this is related
I am also facing issues with the same computer (mac studio m1 ultra)

Below is a description of my experiences:

With blender 3.5.1

Issue 1:

When I initiate the render process one of the following 2 happens.
Either the render will freeze and do nothing. I have to force quit blender in this case
Or blender will crash after the calculation of the scene is finished ( attached is the last crash log).

This happens on relatively heavy projects however the same projects were rending fine in previous blender versions.

Issue 2: Blender will crash at random when changing some settings of a material while in render view.

In blender 3.6 Beta

The same projects render without crashing however when I enter render view, blender freezes without loading any of the scene in render view. After a while it does't go back to solid view and I have to force quit.

None of these issues happen when the engine is set to CPU, only with the GPU so it must be related to the GPU.

Hello I am not sure if this is related I am also facing issues with the same computer (mac studio m1 ultra) Below is a description of my experiences: **With blender 3.5.1** Issue 1: When I initiate the render process one of the following 2 happens. Either the render will freeze and do nothing. I have to force quit blender in this case Or blender will crash after the calculation of the scene is finished ( attached is the last crash log). This happens on relatively heavy projects however the same projects were rending fine in previous blender versions. Issue 2: Blender will crash at random when changing some settings of a material while in render view. **In blender 3.6 Beta** The same projects render without crashing however when I enter render view, blender freezes without loading any of the scene in render view. After a while it does't go back to solid view and I have to force quit. None of these issues happen when the engine is set to CPU, only with the GPU so it must be related to the GPU.

Blender 3.5.1 - m1 crash log.rtf

222 KiB

Michael Parkin-White commented

2023-06-04 14:00:33 +02:00

First-time contributor

@PanagiotisPagonis Thanks for the trace, a lot of the threads in that crash log appear to be waiting for GPU work to complete. This however should not necessarily stall out the app. Curious if this is a possible deadlock situation, although for timeouts, the traces can be unreliable as its not necessarily the problematic threads being reported, rather just where each threads stack pointer was when the application was quit.

I'm curious if the render view is stalling on shader compilation? Curious if given long enough the application will come back to life once whichever stalling work is completed? Either way, this should be asynchronous, but could help narrow down.

As a side note, curious which version of macOS you are running?

Thanks!

@PanagiotisPagonis Thanks for the trace, a lot of the threads in that crash log appear to be waiting for GPU work to complete. This however should not necessarily stall out the app. Curious if this is a possible deadlock situation, although for timeouts, the traces can be unreliable as its not necessarily the problematic threads being reported, rather just where each threads stack pointer was when the application was quit. I'm curious if the render view is stalling on shader compilation? Curious if given long enough the application will come back to life once whichever stalling work is completed? Either way, this should be asynchronous, but could help narrow down. As a side note, curious which version of macOS you are running? Thanks!

Panos Pagonis commented

2023-06-04 14:26:03 +02:00

First-time contributor

Hey @Michael-Parkin-White-Apple

I am on the latest Ventura update 13.4
And I have to admit that before in 13.1 the crashes were much more rare with 3.5.0 and 3.5.1
In fact the only crashes I was experiencing was the one I am describing on issue 2 (random crashes when tweaking material settings in GPU render view)

In 3.6 I've been waiting for about 5 minutes in render view and nothing has changed.

But blender freezes (with the beachball) only when I try to go back in solid view.

Until then I am able to navigate through the scene even select objects (of course all I see is the grey screen and the highlighted areas around the selected object)

What I get in the top left corner is
Sample 0/1024 (Using optimized kernels)
Doesn't that mean the compilation is compete ?

Hey @Michael-Parkin-White-Apple I am on the latest Ventura update 13.4 And I have to admit that before in 13.1 the crashes were much more rare with 3.5.0 and 3.5.1 In fact the only crashes I was experiencing was the one I am describing on issue 2 (random crashes when tweaking material settings in GPU render view) In 3.6 I've been waiting for about 5 minutes in render view and nothing has changed. But blender freezes (with the beachball) only when I try to go back in solid view. Until then I am able to navigate through the scene even select objects (of course all I see is the grey screen and the highlighted areas around the selected object) What I get in the top left corner is _Sample 0/1024 (Using optimized kernels)_ Doesn't that mean the compilation is compete ?

Panos Pagonis commented

2023-06-04 20:21:55 +02:00

First-time contributor

hey @Michael-Parkin-White-Apple

here is an other crash log, not sure if it helps.

This happens in 3.5.1 every time I try to go to render view.
The project does go on render view without a crash after I restart the computer. However rendering does not start (or crashes) despite the restart as it was happening before.

hey @Michael-Parkin-White-Apple here is an other crash log, not sure if it helps. This happens in 3.5.1 every time I try to go to render view. The project does go on render view without a crash after I restart the computer. However rendering does not start (or crashes) despite the restart as it was happening before.

m1 Crash 2.rtf

172 KiB

Panos Pagonis commented

2023-06-05 01:13:05 +02:00

First-time contributor

Hey @Michael-Parkin-White-Apple

I also try to recreate issue 2 on a new scene with only one simpler mesh to demonstrate the crash. Attached is a video with it.
You can see that as soon as I start playing with the settings of the shader it crashes.
However when I reopen the test project and disconnect all of the other nodes it doesn't crash.

The scene is in GPU render view.
The same happens even when the multires is set to lower subdivisions.
Attached you can also find a recreation of the issue using only procedural textures

I hope this is helpful and you can also reproduce the crash too.
In CPU the crash doesn't happen.

Hey @Michael-Parkin-White-Apple I also try to recreate issue 2 on a new scene with only one simpler mesh to demonstrate the crash. Attached is a video with it. You can see that as soon as I start playing with the settings of the shader it crashes. However when I reopen the test project and disconnect all of the other nodes it doesn't crash. The scene is in GPU render view. The same happens even when the multires is set to lower subdivisions. Attached you can also find a recreation of the issue using only procedural textures I hope this is helpful and you can also reproduce the crash too. In CPU the crash doesn't happen.

crash test_3.blend

2.4 MiB

crash test.mov

66 MiB

Lisa-Wiechert commented

2023-06-05 08:40:16 +02:00

First-time contributor

So much has happened over the weekend :)

@Michael-Parkin-White-Apple
Thanks so much for doing all these tests. So far I was still using Blender 3.5.1., but I have now also installed the beta version to see if the same problems will persist. Also, I have not yet updated to Ventura 13.4, I am still running version 13.3.1 (a).
Maybe I will keep that for a while to see if the beta version shows the same problems as 3.5.1. before updating.

So much has happened over the weekend :) @Michael-Parkin-White-Apple Thanks so much for doing all these tests. So far I was still using Blender 3.5.1., but I have now also installed the beta version to see if the same problems will persist. Also, I have not yet updated to Ventura 13.4, I am still running version 13.3.1 (a). Maybe I will keep that for a while to see if the beta version shows the same problems as 3.5.1. before updating.

Lisa-Wiechert commented

2023-06-05 17:19:39 +02:00

First-time contributor

Well, I have a new crash report. This time working in Blender 3.6 beta, and the crash happened after saving and pressing cmd+Q to end Blender. The crash report is attached!

Blender_Crash_06-05-23.txt

102 KiB

Michael Parkin-White commented

2023-06-07 12:04:00 +02:00

First-time contributor

Thanks Lisa, I can look into this as well, I appreciate the bug reports and the time you've taken to test on other platforms!

The main thing we would like to understand is whether the original crashes you were experiencing are still occurring in 3.6.0, as these issues are our highest priority. It sounds like the cmd+Q issue may be something separate, though this is still something I can look into.

@PanagiotisPagonis Thank you for providing the files and the additional information. This is curious, but I will continue to investigate. I've not been able to reproduce this on my local machine yet, but will continue investigating.

Thanks all!

Thanks Lisa, I can look into this as well, I appreciate the bug reports and the time you've taken to test on other platforms! The main thing we would like to understand is whether the original crashes you were experiencing are still occurring in 3.6.0, as these issues are our highest priority. It sounds like the cmd+Q issue may be something separate, though this is still something I can look into. @PanagiotisPagonis Thank you for providing the files and the additional information. This is curious, but I will continue to investigate. I've not been able to reproduce this on my local machine yet, but will continue investigating. Thanks all!

Panos Pagonis commented

2023-06-07 17:13:03 +02:00

First-time contributor

thanks a lot @Michael-Parkin-White-Apple !

I was able to recreate the issue I experience using one of blender’s files
https://www.blender.org/download/demo-files/

( “Change” - Open Movie)

Attached is is a video demonstrating what is happening, but in a few words:

I change the engine from eevee to cycles GPU .
I go to render view, nothing happens just as described above
When i try to go back in solid view blender freezes.
The same happens with some of my heavy(ish) project in 3.6.0 beta

In 3.5.1 the same project responds in render view as it should be.

When I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)
I manage to reopen the project after a few crashes.

I hope it helps!

thanks a lot @Michael-Parkin-White-Apple ! I was able to recreate the issue I experience using one of blender’s files https://www.blender.org/download/demo-files/ ( “Change” - Open Movie) Attached is is a video demonstrating what is happening, but in a few words: I change the engine from eevee to cycles GPU . I go to render view, nothing happens just as described above When i try to go back in solid view blender freezes. The same happens with some of my heavy(ish) project in 3.6.0 beta In 3.5.1 the same project responds in render view as it should be. When I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached) I manage to reopen the project after a few crashes. I hope it helps!

3.6.0 crash after trying to reopen test file.rtf

198 KiB

freeze render view 3.6 and 3.5.1.mp4

22 MiB

Michael Parkin-White commented

2023-06-08 14:31:54 +02:00

First-time contributor

Thanks Panos, we're able to reproduce this one.
As this appears to be a Cycles Metal Backend issue, handing over to @Michael-Jones

Thanks Panos, we're able to reproduce this one. As this appears to be a Cycles Metal Backend issue, handing over to @Michael-Jones

👍 1

Germano Cavalcante commented

2023-06-27 21:17:08 +02:00

Thanks Panos, we're able to reproduce this one.

I'll confirm the report then.
I've updated the description to show the steps described in the comment.

> Thanks Panos, we're able to reproduce this one. I'll confirm the report then. I've updated the description to show the steps described in the comment.

Germano Cavalcante added

Module

Render & Cycles

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 3.5.1 keeps crashing on occasion #107941