blender/blender
148
472
Fork 692
Code Issues 6.7k Pull Requests 896 Projects 18 Wiki Activity

Blender 3.5.1 + Mac + Metal + Crash #106607

New Issue
Closed
opened 2023-04-06 02:48:34 +02:00 by Ric-Lopez · 28 comments
Ric-Lopez commented 2023-04-06 02:48:34 +02:00
Copy Link

System Information
Operating system: MONTEREY 12.6.3
Graphics card: AMD Radeon Pro 5500 XT 8 GB

Blender Version
Broken: Blender 3.5.1
Worked: Blender 3.4.1

Short description of error
Blender 3.4.1 will render a given scene with "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE" in 1 min 58 sec

Blender 3.5 and 3.5.1 will crash on the same scene set on "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE" -
It has to be run with "RENDER PROPERTIES" -> "DEVICE" set to "CP" and now takes 5 min 53 sec.

I have lost computing power with the latest versions.

Exact steps for others to reproduce the error
Just run the file with GPU BACKEND turned on and "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE"

I could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send

**System Information** Operating system: MONTEREY 12.6.3 Graphics card: AMD Radeon Pro 5500 XT 8 GB **Blender Version** Broken: Blender 3.5.1 Worked: Blender 3.4.1 **Short description of error** Blender 3.4.1 will render a given scene with "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE" in 1 min 58 sec Blender 3.5 and 3.5.1 will crash on the same scene set on "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE" - It has to be run with "RENDER PROPERTIES" -> "DEVICE" set to "CP" and now takes 5 min 53 sec. I have lost computing power with the latest versions. **Exact steps for others to reproduce the error** Just run the file with GPU BACKEND turned on and "RENDER PROPERTIES" -> "DEVICE" set to "GPU COMPUTE" I could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send
Ric-Lopez added the
Severity
Normal
Status
Needs Triage
Type
Report
 labels 2023-04-06 02:48:34 +02:00
Germano Cavalcante commented 2023-04-06 18:30:45 +02:00
Member
Copy Link

The triage team needs to replicate the problem (and maybe reform and simplify the report) in order to forward it to the developers (in this case, the Cycles team).

It's a straightforward process, and it's not up to the triage team to investigate and resolve technical issues.

So I would need a file (preferably simplified) to be able to try to replicate it on the Mac I have available.

The triage team needs to replicate the problem (and maybe reform and simplify the report) in order to forward it to the developers (in this case, the Cycles team). It's a straightforward process, and it's not up to the triage team to investigate and resolve technical issues. So I would need a file (preferably simplified) to be able to try to replicate it on the Mac I have available.
Germano Cavalcante added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-04-06 18:30:54 +02:00
Ric-Lopez commented 2023-04-06 20:49:53 +02:00
Author
Copy Link

Thanks - I will create a new file and replicate the issue here - then send it to you

Thanks - I will create a new file and replicate the issue here - then send it to you
Ric-Lopez commented 2023-04-06 22:05:20 +02:00
Author
Copy Link
I have 3 files here
All the same scene, a free scene downloaded from CGTrader.
The scene in the folder "Blender 3.5.1 all Metal" crashed after a few minutes
...the image "3.5.1 Amount Rendered before crash.jpg" shows how much was rendered before the crash
...the image "3.5.1 Render Setup.jpg" and "3.5.1 System Prefs.jpg" show the system and render settings
------------------------------------------------
The scene in the folder "Blender 3.4.1 Metal" also has images for the system and render settings.
It rendered completely in 14 minutes - the final image is "CozyRoom-Render"
Let me know what else you might need from me.

I had to break the textures up into smaller files for upload - they apply to both scenes

Ric

The remaining texture files are in the comment that follows

###### I have 3 files here ###### All the same scene, a free scene downloaded from CGTrader. ###### The scene in the folder "Blender 3.5.1 all Metal" crashed after a few minutes ###### ...the image "3.5.1 Amount Rendered before crash.jpg" shows how much was rendered before the crash ###### ...the image "3.5.1 Render Setup.jpg" and "3.5.1 System Prefs.jpg" show the system and render settings ###### ------------------------------------------------ ###### The scene in the folder "Blender 3.4.1 Metal" also has images for the system and render settings. ###### It rendered completely in 14 minutes - the final image is "CozyRoom-Render" ###### Let me know what else you might need from me. ***I had to break the textures up into smaller files for upload - they apply to both scenes*** ###### ###### Ric ###### ### The remaining texture files are in the comment that follows
Blender 3.4.1 Metal.zip
46 MiB
CozyRoom-Render.tif.zip
72 MiB
textures-02.zip
90 MiB
textures-01.zip
90 MiB
Blender 3.5.1 all Metal.zip
46 MiB
Ric-Lopez commented 2023-04-06 22:07:39 +02:00
Author
Copy Link

Here are the remaining texture files

#### Here are the remaining texture files
textures-05.zip
40 MiB
textures-06.zip
22 MiB
textures-03.zip
63 MiB
textures-04.zip
36 MiB
Germano Cavalcante added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2023-04-06 22:10:32 +02:00
Germano Cavalcante commented 2023-04-06 22:12:34 +02:00
Member
Copy Link

Thanks for the file. Now I can only test it on Monday. Someone else can confirm in the mean time

Thanks for the file. Now I can only test it on Monday. Someone else can confirm in the mean time
Germano Cavalcante commented 2023-04-12 21:01:22 +02:00
Member
Copy Link

Thanks for the files, but I can't replicate the problem and unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.

Looking at the hardware, it is possible that this problem is related to the same one described in #106551 (Blender on Mac freezes when working on shader nodes).

As the file is complex, maybe it's worth waiting for this other issue to be fixed before testing again.

System Information
Operating system: macOS-13.2.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 1.2

Thanks for the files, but I can't replicate the problem and unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem. Looking at the hardware, it is possible that this problem is related to the same one described in #106551 (Blender on Mac freezes when working on shader nodes). As the file is complex, maybe it's worth waiting for this other issue to be fixed before testing again. --- **System Information** Operating system: macOS-13.2.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 1.2
Germano Cavalcante added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-04-12 21:01:40 +02:00
Ric-Lopez commented 2023-04-12 21:37:00 +02:00
Author
Copy Link

Germano
Thanks, I will try to render the file referenced in #106551 - just to see what happens, as well as my own with the latest builds.

In your opinion, do you think that this an AMD issue? And would a newer AMD card (as an eGPU) help?

Germano Thanks, I will try to render the file referenced in #106551 - just to see what happens, as well as my own with the latest builds. In your opinion, do you think that this an AMD issue? And would a newer AMD card (as an eGPU) help?
Ric-Lopez commented 2023-04-13 00:16:00 +02:00
Author
Copy Link

Tried the new Blender build with the file I sent (above) and Blender with Metal enabled and GPU Metal backend on and it still crashes partway throough a render (single frame render)

I tried the file referenced #106551 and have no trouble maneuvering through that file or even rendering it.

### How do I get you a bug report?

Tried the new Blender build with the file I sent (above) and Blender with Metal enabled and GPU Metal backend on and it still crashes partway throough a render (single frame render) I tried the file referenced #106551 and have no trouble maneuvering through that file or even rendering it. _**### How do I get you a bug report?**_
Ric-Lopez commented 2023-04-13 02:00:27 +02:00
Author
Copy Link

In preliminary tests, it appears that I may have a solution.

In the "preferences" => "Cycles Render Devices" => "Matal Tab", I had "AMD Radeon Pro 5500 XT" selected AND "Intel Core 19-10910 CPU @ 3.60GHz" selected as well.

When I unchecked the "Intel Core...CPU" and rendered, there was NO Crash.

I thought I had to have them both selected to have a CPU and GPU available to the Application.

I guess not!

In preliminary tests, it appears that I may have a solution. In the "preferences" => "Cycles Render Devices" => "Matal Tab", I had "AMD Radeon Pro 5500 XT" selected AND "Intel Core 19-10910 CPU @ 3.60GHz" selected as well. When I unchecked the "Intel Core...CPU" and rendered, there was NO Crash. I thought I had to have them both selected to have a CPU and GPU available to the Application. I guess not!
Metal Prefs.jpg
52 KiB
Metal Prefs.jpg
Germano Cavalcante commented 2023-04-13 15:57:18 +02:00
Member
Copy Link

I'm not sure if another GPU from AMD will solve the problem.
Since the issue only occurs with mixed CPU + GPU rendering, it is possible that this is a memory issue (that the hardware has reached the limits of available RAM). In these cases GPUs with More VRAM can help.

But that doesn't explain why the same file works in 3.4.1 and not in 3.5.1

In addition to #106551, there is another issue related to AMD GPUs that is being investigated. See #106657

I'm not sure if another GPU from AMD will solve the problem. Since the issue only occurs with mixed CPU + GPU rendering, it is possible that this is a memory issue (that the hardware has reached the limits of available RAM). In these cases GPUs with More VRAM can help. But that doesn't explain why the same file works in 3.4.1 and not in 3.5.1 In addition to #106551, there is another issue related to AMD GPUs that is being investigated. See #106657
Ric-Lopez commented 2023-04-13 17:06:10 +02:00
Author
Copy Link

I image these are AMD issues, but I could not reproduce the issue cited in #106657
on my Intel Mac

iMac (Retina 5K, 27-inch, 2020)
3.6 GHz 10-Core Intel Core i9
128 GB 2667 MHz DDR4
AMD Radeon Pro 5500 XT 8 GB

I image these are AMD issues, but I could not reproduce the issue cited in #106657 on my Intel Mac iMac (Retina 5K, 27-inch, 2020) 3.6 GHz 10-Core Intel Core i9 128 GB 2667 MHz DDR4 AMD Radeon Pro 5500 XT 8 GB
Germano Cavalcante commented 2023-04-13 17:40:01 +02:00
Member
Copy Link

Did you check if you also enabled the Intel CPU to render in blender 3.4.1?

Unless this is a regression, memory issues due to very complex scenes are not currently considered a bug.

Developers try to improve Blender to handle these cases of system running out of memory gracefully with error messages or something like that, but these cases are not always caught.

Did you check if you also enabled the Intel CPU to render in blender 3.4.1? Unless this is a regression, memory issues due to very complex scenes are not currently considered a bug. Developers try to improve Blender to handle these cases of system running out of memory gracefully with error messages or something like that, but these cases are not always caught.
Ric-Lopez commented 2023-04-13 19:41:14 +02:00
Author
Copy Link

Yes, I have always - up til now, had both check boxes checked -

Yes, I have always - up til now, had both check boxes checked -
Screen Shot 2023-04-13 at 1.40.47 PM.jpg
36 KiB
Screen Shot 2023-04-13 at 1.40.47 PM.jpg
Ric-Lopez commented 2023-04-23 21:29:47 +02:00
Author
Copy Link

Germano - am I the only one with this issue?
It remains an issue even in today's build in the sample file "Victor" even with AMD Radeon..." Turned On and "Intel Core...CPU" turned off and Metal Checked.

My computer has plenty of RAM 128 GB - But the AMD video card has only 8 GB - How can I determine if the issue is video RAM? There is no feedback from Blender as to the issue.

This is becomming very frustrating - Blender 3.4.1 still works without crashing.

I it just a matter of AMD updating Drivers?

Germano - am I the only one with this issue? It remains an issue even in today's build in the sample file "Victor" even with AMD Radeon..." Turned On and "Intel Core...CPU" turned off and Metal Checked. My computer has plenty of RAM 128 GB - But the AMD video card has only 8 GB - How can I determine if the issue is video RAM? There is no feedback from Blender as to the issue. This is becomming very frustrating - Blender 3.4.1 still works without crashing. I it just a matter of AMD updating Drivers?
Germano Cavalcante commented 2023-04-24 15:44:49 +02:00
Member
Copy Link

I tested it once, but as the file is so complex and takes a long time to render, I'm holding back from testing it again.

This report seems to fall under the "Too complex file report, where user could not simplify enough" scenario from Triaging_Playbook.

It also appears to be an "out of memory" issue (often not considered a bug unless it's a regression).

Recently there have been some improvements made to how Metal handles memory when rendering with Eevee, I'm not sure if this affects Cycles, but we can see that development in this area.

Have you checked if, by any chance, you enabled MetalRT in 3.5?

I tested it once, but as the file is so complex and takes a long time to render, I'm holding back from testing it again. This report seems to fall under the "Too complex file report, where user could not simplify enough" scenario from [Triaging_Playbook](https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook). It also appears to be an "out of memory" issue (often not considered a bug unless it's a regression). Recently there have been some improvements made to how Metal handles memory when rendering with Eevee, I'm not sure if this affects Cycles, but we can see that development in this area. Have you checked if, by any chance, you enabled MetalRT in 3.5?
Germano Cavalcante added
Status
Needs Triage
 and removed
Status
Needs Information from User
 labels 2023-04-24 15:45:02 +02:00
Germano Cavalcante added the
Interest
Metal
 label 2023-04-24 15:56:18 +02:00
Ric-Lopez commented 2023-04-24 17:46:25 +02:00
Author
Copy Link

Thanks for getting back to me - MetalRT does not appear for me in version 3.5.1 downloaded 2 days ago on my intel Mac - is there another way to enable it?

Thanks for getting back to me - MetalRT does not appear for me in version 3.5.1 downloaded 2 days ago on my intel Mac - is there another way to enable it?
Pratik Borhade commented 2023-07-06 08:40:46 +02:00
Member
Copy Link

Hi, does crash/freeze persist in 3.6-release?: https://builder.blender.org/download/daily/
Crash logs will help to identify the problem: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#macos
BTW, are you performing viewport rendering or is it a final render Render > Render image/animaton?

Hi, does crash/freeze persist in 3.6-release?: https://builder.blender.org/download/daily/ Crash logs will help to identify the problem: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#macos BTW, are you performing viewport rendering or is it a final render `Render > Render image/animaton`?
Pratik Borhade added
Status
Needs Information from User
 and removed
Status
Needs Triage
 labels 2023-07-06 08:40:55 +02:00
Ric-Lopez commented 2023-07-06 16:28:32 +02:00
Author
Copy Link

it has been much better since the changes were made to the Metal back end.

But I find I must turn the render chunks (render memory) down to 512 or 256 (or less) for a complex or large render to be done without a crash.

So it does appear, at the moment, that 8 GB video ram is only barely enough.

I would love to know if anyone has had good luck with eGPU arrangements on the Mac, and whart the configuration is.....

it has been much better since the changes were made to the Metal back end. But I find I must turn the render chunks (render memory) down to 512 or 256 (or less) for a complex or large render to be done without a crash. So it does appear, at the moment, that 8 GB video ram is only barely enough. I would love to know if anyone has had good luck with eGPU arrangements on the Mac, and whart the configuration is.....
Pratik Borhade commented 2023-07-07 05:16:48 +02:00
Member
Copy Link

Thanks.

These questions are still unanswered :/
As far as I understand, Cycles render is triggering the crash, right?

Thanks. >- Crash logs will help to identify the problem: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#macos >- BTW, are you performing viewport rendering or is it a final render Render > Render image/animaton? These questions are still unanswered :/ As far as I understand, Cycles render is triggering the crash, right?
Pratik Borhade commented 2023-07-18 07:56:13 +02:00
Member
Copy Link

poke

poke
Ric-Lopez commented 2023-07-18 20:01:47 +02:00
Author
Copy Link

I'm sorry, as I said above when it has crashed , I reduce the render chunks (render memory) and it seems to render through after that.

However - when it does crash again I will collect the crash report.

I will attempt to male it crash and send the report along.

I'm sorry, as I said above when it has crashed , I reduce the render chunks (render memory) and it seems to render through after that. However - when it does crash again I will collect the crash report. I will attempt to male it crash and send the report along.
Ric-Lopez commented 2023-07-18 21:27:55 +02:00
Author
Copy Link

I am now using Mac OS Venturea 13.4.1

I ran the file twice

the first time it did not crash but stopped render with the message that I was out of GPU memory that file is:
"Blender-2023-07-18-150652"

The second time it did crash and the report is: "Blender-2023-07-18-152121.txt"

And at that time Mac OS gace me a crash report that is: "Mac Os Crash of Blender Report"

I am now using Mac OS Venturea 13.4.1 I ran the file twice the first time it did not crash but stopped render with the message that I was out of GPU memory that file is: "Blender-2023-07-18-150652" The second time it did crash and the report is: "Blender-2023-07-18-152121.txt" And at that time Mac OS gace me a crash report that is: "Mac Os Crash of Blender Report"
Blender-2023-07-18-150652.txt
105 KiB
Blender-2023-07-18-152121.txt
106 KiB
Ric-Lopez commented 2023-07-18 21:29:13 +02:00
Author
Copy Link

that last file is here

that last file is here
Mac Os Crash of Blender Report.txt
192 KiB
Pratik Borhade commented 2023-07-19 09:21:25 +02:00
Member
Copy Link

Hi, thanks. Thread 51 crashed when rendering the scene.

the first time it did not crash but stopped render with the message that I was out of GPU memory that file is:

How much memory your system have and how much is utilized during render?
Could be a crash due to memory management. Not very sure.
BTW, can you simplify the file and pack textures within the file?
To pack textures: File > External Data > Pack Resources -> save .blend file

Thread 51 Crashed:
0   libsystem_kernel.dylib        	    0x7ff8106df1f2 __pthread_kill + 10
1   libsystem_pthread.dylib       	    0x7ff810716ee6 pthread_kill + 263
2   libsystem_c.dylib             	    0x7ff81063dbdf __abort + 139
3   libsystem_c.dylib             	    0x7ff81063db54 abort + 138
4   libsystem_c.dylib             	    0x7ff81063ce5e __assert_rtn + 314
5   Metal                         	    0x7ff819f0c202 MTLReportFailure.cold.1 + 43
6   Metal                         	    0x7ff819ee7caf MTLReportFailure + 529
7   Metal                         	    0x7ff819dda0ed -[_MTLCommandEncoder dealloc] + 123
8   libobjc.A.dylib               	    0x7ff81038861c AutoreleasePoolPage::releaseUntil(objc_object**) + 168
9   libobjc.A.dylib               	    0x7ff810385979 objc_autoreleasePoolPop + 227
10  CoreFoundation                	    0x7ff8107b5f3e _CFAutoreleasePoolPop + 22
11  Foundation                    	    0x7ff8116518dc -[NSAutoreleasePool drain] + 133
12  Blender                       	       0x10ef73a90 blender::gpu::MTLBackend::render_end() + 48
13  Blender                       	       0x107ea4734 DRW_render_context_disable + 84
14  Blender                       	       0x109d26f3c ccl::PathTraceDisplay::update_end() + 28
15  Blender                       	       0x109d1b5f1 ccl::PathTrace::update_display(ccl::RenderWork const&) + 881
16  Blender                       	       0x109d197fa ccl::PathTrace::render_pipeline(ccl::RenderWork) + 426
17  Blender                       	       0x109d19615 ccl::PathTrace::render(ccl::RenderWork const&) + 117
18  Blender                       	       0x109c982ef ccl::Session::run_main_render_loop() + 831
19  Blender                       	       0x109c99083 ccl::Session::thread_render() + 259
20  Blender                       	       0x109c96b88 ccl::Session::thread_run() + 168
21  Blender                       	       0x10de14dd3 ccl::thread::run(void*) + 19
22  libsystem_pthread.dylib       	    0x7ff8107171d3 _pthread_start + 125
23  libsystem_pthread.dylib       	    0x7ff810712bd3 thread_start + 15
Hi, thanks. Thread 51 crashed when rendering the scene. > the first time it did not crash but stopped render with the message that I was out of GPU memory that file is: How much memory your system have and how much is utilized during render? Could be a crash due to memory management. Not very sure. BTW, can you simplify the file and pack textures within the file? To pack textures: `File > External Data > Pack Resources` -> save .blend file ``` Thread 51 Crashed: 0 libsystem_kernel.dylib 0x7ff8106df1f2 __pthread_kill + 10 1 libsystem_pthread.dylib 0x7ff810716ee6 pthread_kill + 263 2 libsystem_c.dylib 0x7ff81063dbdf __abort + 139 3 libsystem_c.dylib 0x7ff81063db54 abort + 138 4 libsystem_c.dylib 0x7ff81063ce5e __assert_rtn + 314 5 Metal 0x7ff819f0c202 MTLReportFailure.cold.1 + 43 6 Metal 0x7ff819ee7caf MTLReportFailure + 529 7 Metal 0x7ff819dda0ed -[_MTLCommandEncoder dealloc] + 123 8 libobjc.A.dylib 0x7ff81038861c AutoreleasePoolPage::releaseUntil(objc_object**) + 168 9 libobjc.A.dylib 0x7ff810385979 objc_autoreleasePoolPop + 227 10 CoreFoundation 0x7ff8107b5f3e _CFAutoreleasePoolPop + 22 11 Foundation 0x7ff8116518dc -[NSAutoreleasePool drain] + 133 12 Blender 0x10ef73a90 blender::gpu::MTLBackend::render_end() + 48 13 Blender 0x107ea4734 DRW_render_context_disable + 84 14 Blender 0x109d26f3c ccl::PathTraceDisplay::update_end() + 28 15 Blender 0x109d1b5f1 ccl::PathTrace::update_display(ccl::RenderWork const&) + 881 16 Blender 0x109d197fa ccl::PathTrace::render_pipeline(ccl::RenderWork) + 426 17 Blender 0x109d19615 ccl::PathTrace::render(ccl::RenderWork const&) + 117 18 Blender 0x109c982ef ccl::Session::run_main_render_loop() + 831 19 Blender 0x109c99083 ccl::Session::thread_render() + 259 20 Blender 0x109c96b88 ccl::Session::thread_run() + 168 21 Blender 0x10de14dd3 ccl::thread::run(void*) + 19 22 libsystem_pthread.dylib 0x7ff8107171d3 _pthread_start + 125 23 libsystem_pthread.dylib 0x7ff810712bd3 thread_start + 15 ```
Ric-Lopez commented 2023-07-19 19:18:43 +02:00
Author
Copy Link

The computer has 128 GB Ram - The Video card has 8 GB video Ram

I will have to locate a new file that causes the same problem - I got this one online and it is missing some images and uses plugins I do not have.

Perhaps that caused the crash?

The computer has 128 GB Ram - The Video card has 8 GB video Ram I will have to locate a new file that causes the same problem - I got this one online and it is missing some images and uses plugins I do not have. Perhaps that caused the crash?
Pratik Borhade commented 2023-07-20 06:52:19 +02:00
Member
Copy Link

missing some images and uses plugins

That could be the culprit. But hard to tell from crash logs because it has only reported the function calls related to rendering.

> missing some images and uses plugins That could be the culprit. But hard to tell from crash logs because it has only reported the function calls related to rendering.
Pratik Borhade commented 2024-03-01 05:55:05 +01:00
Member
Copy Link

@Ric-Lopez hi, still encountering the crash in 4.1 beta?: https://builder.blender.org/download/daily/

@Ric-Lopez hi, still encountering the crash in 4.1 beta?: https://builder.blender.org/download/daily/
Ric-Lopez commented 2024-03-01 16:52:13 +01:00
Author
Copy Link

I think we're good now I believe I had to change the render chunk size in order to keep the application from crashing

I think we're good now I believe I had to change the render chunk size in order to keep the application from crashing
Blender Bot added
Status
Archived
 and removed
Status
Needs Information from User
 labels 2024-03-01 16:52:18 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Alembic

  
Interest
Animation & Rigging

  
Interest
Asset System
Asset datablocks, libraries, browser and shelf

  
Interest
Audio

  
Interest
Automated Testing

  
Interest
Blender Asset Bundle

  
Interest
BlendFile

  
Interest
Collada

  
Interest
Compatibility
Backward and forward compatibility

  
Interest
Compositing

  
Interest
Core

  
Interest
Cycles

  
Interest
Dependency Graph

  
Interest
Development Management

  
Interest
EEVEE

  
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
Viewport & EEVEE

  
Interest
Virtual Reality

  
Interest
Vulkan

  
Interest
Wayland
Wayland windowing on Unix

  
Interest
Workbench

  
Interest: X11

Xorg/X11 windowing

  
Legacy
Asset Browser Project

Archived

  
Legacy
Blender 2.8 Project

Archived

  
Legacy
Milestone 1: Basic, Local Asset Browser

Archived

  
Legacy
OpenGL Error

Archived

  
Meta
Good First Issue

  
Meta
Papercut

  
Meta
Retrospective

  
Meta
Security
Related to security, https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  
Module
Animation & Rigging

  
Module
Core

  
Module
Development Management

  
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

  
Module
Viewport & EEVEE

  
Platform
FreeBSD

  
Platform
Linux

  
Platform
macOS

  
Platform
Windows

  
Severity
High

  
Severity
Low

  
Severity
Normal

  
Severity
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

Archived

  
Type
Report

Archived

  
Type
To Do

No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#106607
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?