Blender crashes during baking process #102640

New Issue

David Gonzalez · 2022-11-20T22:08:59+01:00

David Gonzalez commented

2022-11-20 22:08:59 +01:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
CPU: AMD Ryzen 7 5800X
RAM: 32 GB DDR4 @ 3200 MHz
Graphics card: NVIDIA GeForce RTX 3090 FE/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98

Blender Version
Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: Don't know as I didn't use Blender for a long time

Short description of error
Blender crashes during baking process. For baking I use an addon called "Simple Bake" and I'm already in contact with the developer as I suspected an issue regarding his addon but he's clueless what is causing the crash because the console doesn't display an error. You'll find the console output file attached.

That's why I try to reach out to you now, hoping that you can help us solving the issue. I would really appreciate it!

Exact steps for others to reproduce the error

load the .blend file
start the bake with Simple Bake Add-on in foreground. The bake process starts and Blender crashes after a few seconds.
I'd send the .blend file to the developer of Simple Bake, so he can check if the issue is reproducible but on his side the bake works without issues.

Please let me know if you need more information.

blender_console_output.txt
blender_debug_output.txt
SimpleBakeTest.blend
NOTE: Crash happens only with add-on

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits CPU: AMD Ryzen 7 5800X RAM: 32 GB DDR4 @ 3200 MHz Graphics card: NVIDIA GeForce RTX 3090 FE/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98 **Blender Version** Broken: version: 3.3.1, branch: master, commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: Don't know as I didn't use Blender for a long time **Short description of error** Blender crashes during baking process. For baking I use an addon called "Simple Bake" and I'm already in contact with the developer as I suspected an issue regarding his addon but he's clueless what is causing the crash because the console doesn't display an error. You'll find the console output file attached. That's why I try to reach out to you now, hoping that you can help us solving the issue. I would really appreciate it! **Exact steps for others to reproduce the error** - load the .blend file - start the bake with `Simple Bake` Add-on in foreground. The bake process starts and Blender crashes after a few seconds. I'd send the .blend file to the developer of Simple Bake, so he can check if the issue is reproducible but on his side the bake works without issues. Please let me know if you need more information. [blender_console_output.txt](https://archive.blender.org/developer/F13952468/blender_console_output.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13984066/blender_debug_output.txt) [SimpleBakeTest.blend](https://archive.blender.org/developer/F13960393/SimpleBakeTest.blend) NOTE: Crash happens only with add-on

David Gonzalez commented

2022-11-20 22:08:59 +01:00

Added subscriber: @Bango

Pratik Borhade commented

2022-11-21 06:17:28 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-11-21 06:17:28 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Pratik Borhade commented

2022-11-21 06:17:28 +01:00

Hi, thanks for the report. Does this only happen when invoking bake from add-on?
Please share .blend file

Hi, thanks for the report. Does this only happen when invoking bake from add-on? Please share .blend file

David Gonzalez commented

2022-11-22 13:39:29 +01:00

Hi Pratik,

Thanks for the quick response!

Yes, it seems like Blender only crashes if I try to bake with the PBR Bake option of Simple Bake. Blender doesn't crash with Blender's internal baking method or if I try to bake with the Cycles Bake option of Simple Bake but this is very lengthy for my needs because a) I don't know how to bake all the nodes which are contained in the material with the Cycles baking method and b) it would definitely be very time consuming if I want to bake an asset with multiple objects and materials. What I need is a way to bake all Materials and textures into one texture set at once! Simple Bake's PBR method seems to offer what I'm searching for... if it would work as intended.

The developer of Simple Bake tries to help me solve the issue but he's at his wit's end because Blender doesn't output an error and it seems like I'm the only one of his customers having issues baking with this method.

A .blend file is attached to this post{F13960393}.

Hi Pratik, Thanks for the quick response! Yes, it seems like Blender only crashes if I try to bake with the PBR Bake option of Simple Bake. Blender doesn't crash with Blender's internal baking method or if I try to bake with the Cycles Bake option of Simple Bake but this is very lengthy for my needs because a) I don't know how to bake all the nodes which are contained in the material with the Cycles baking method and b) it would definitely be very time consuming if I want to bake an asset with multiple objects and materials. What I need is a way to bake all Materials and textures into one texture set at once! Simple Bake's PBR method seems to offer what I'm searching for... if it would work as intended. The developer of Simple Bake tries to help me solve the issue but he's at his wit's end because Blender doesn't output an error and it seems like I'm the only one of his customers having issues baking with this method. A .blend file is attached to this post{[F13960393](https://archive.blender.org/developer/F13960393/SimpleBakeTest.blend)}.

Pratik Borhade commented

2022-12-01 04:59:48 +01:00

Hi, thanks for the file. I don't have subscription of the add-on so I won't be able to investigate this further.
Also it's hard to tell whether issue is in blender code or an add-on itself.
Could you run blender with debug options? it might give useful information regarding the crash:

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the
error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them
to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Hi, thanks for the file. I don't have subscription of the add-on so I won't be able to investigate this further. Also it's hard to tell whether issue is in blender code or an add-on itself. Could you run blender with debug options? it might give useful information regarding the crash: > Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the > error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them > to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your > username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

David Gonzalez commented

2022-12-01 14:17:39 +01:00

Hi, thanks for replying!

I'll send you the debug log and the system information which you'll find attached. However, I didn't receive a crash file again.

Please let me know if you need more information.

blender_debug_output.txt

blender_system_info.txt

Hi, thanks for replying! I'll send you the debug log and the system information which you'll find attached. However, I didn't receive a crash file again. Please let me know if you need more information. [blender_debug_output.txt](https://archive.blender.org/developer/F13984066/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13984065/blender_system_info.txt)

Pratik Borhade commented

2022-12-02 06:08:15 +01:00

Thanks for the logs. I couldn't really spot crash related info in file. Most likely to be a bug in add-on itself but its hard to come on that conclusion unless we test the add-on.
Testing this in a debug build might help.

Thanks for the logs. I couldn't really spot crash related info in file. Most likely to be a bug in add-on itself but its hard to come on that conclusion unless we test the add-on. Testing this in a debug build might help.

Pratik Borhade commented

2022-12-02 10:31:32 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Pratik Borhade closed this issue

2022-12-02 10:31:32 +01:00

Pratik Borhade commented

2022-12-02 10:31:32 +01:00

Closing this report since I need access to the add-on otherwise it's not possible to investigate this further.
Thanks again for the report!

Closing this report since I need access to the add-on otherwise it's not possible to investigate this further. Thanks again for the report!

David Gonzalez commented

2022-12-02 13:49:41 +01:00

Thanks, for coming back!

Shouldn't the log files then output an error that is attributable to the addon and why don't I get a crash file?

I can't believe that the addon is responsible for this. Otherwise, how should the developer of the addon determine that a bug inside his addon is responsible for the crash if Blender doesn't output anything about it?

I would appreciate it if you let this ticket open, at least until you can definitely exclude a misconduct by Blender.

Thanks, for coming back! Shouldn't the log files then output an error that is attributable to the addon and why don't I get a crash file? I can't believe that the addon is responsible for this. Otherwise, how should the developer of the addon determine that a bug inside his addon is responsible for the crash if Blender doesn't output anything about it? I would appreciate it if you let this ticket open, at least until you can definitely exclude a misconduct by Blender.

David Gonzalez commented

2022-12-02 14:02:06 +01:00

Besides that, the log file does contain following info and warnings:

INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 244 is being recompiled based on GL state.
INFO (gpu.debug): Notification : Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers.
WARN (gpu.debug): Overlay > Outlines : Program/shader state performance warning: Vertex shader in program 183 is being recompiled based on GL state.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 11 is being recompiled based on GL state.

Isn't this relevant to the issue?

Besides that, the log file does contain following info and warnings: ``` INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping. WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 244 is being recompiled based on GL state. INFO (gpu.debug): Notification : Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers. WARN (gpu.debug): Overlay > Outlines : Program/shader state performance warning: Vertex shader in program 183 is being recompiled based on GL state. WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 11 is being recompiled based on GL state. ``` Isn't this relevant to the issue?

Pratik Borhade commented

2022-12-02 14:03:22 +01:00

Changed status from 'Archived' to: 'Needs Triage'

Pratik Borhade reopened this issue

2022-12-02 14:03:22 +01:00

Germano Cavalcante commented

2022-12-02 15:12:28 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-12-02 15:12:28 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Germano Cavalcante commented

2022-12-02 15:12:28 +01:00

In #102640#1454437, @Bango wrote:
Besides that, the log file does contain following info and warnings:

INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 244 is being recompiled based on GL state.
INFO (gpu.debug): Notification : Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers.
WARN (gpu.debug): Overlay > Outlines : Program/shader state performance warning: Vertex shader in program 183 is being recompiled based on GL state.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 11 is being recompiled based on GL state.

Isn't this relevant to the issue?

These messages are common. Many of them are false alerts indicating an incomplete state, which happens when the gpu object is still being configured.
There are plans to clear these messages, but they are highly dependent on the GPU and the order in which the API is called.

Without a crash log and without being able to replicate the problem without having access to the addon it is very difficult for the developer to identify the cause and fix the problem.
It's also not clear if it's a driver issue or if it's exceeded hardware memory limits.
In order for us to investigate this issue, please provide a .blend file with simple steps to replicate the issue with the tools available by default in Blender.

> In #102640#1454437, @Bango wrote: > Besides that, the log file does contain following info and warnings: > > ``` > INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping. > WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 244 is being recompiled based on GL state. > INFO (gpu.debug): Notification : Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers. > WARN (gpu.debug): Overlay > Outlines : Program/shader state performance warning: Vertex shader in program 183 is being recompiled based on GL state. > WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 11 is being recompiled based on GL state. > > ``` > > Isn't this relevant to the issue? These messages are common. Many of them are false alerts indicating an incomplete state, which happens when the gpu object is still being configured. There are plans to clear these messages, but they are highly dependent on the GPU and the order in which the API is called. --- Without a crash log and without being able to replicate the problem without having access to the addon it is very difficult for the developer to identify the cause and fix the problem. It's also not clear if it's a driver issue or if it's exceeded hardware memory limits. In order for us to investigate this issue, please provide a .blend file with simple steps to replicate the issue with the tools available by default in Blender.

David Gonzalez commented

2022-12-02 16:33:06 +01:00

In #102640#1454475, @mano-wii wrote:
These messages are common. Many of them are false alerts indicating an incomplete state, which happens when the gpu object is still being configured.
There are plans to clear these messages, but they are highly dependent on the GPU and the order in which the API is called.

Okay, thanks for the info. Good to know that those messages are false alerts, so I don't have to be concerned about them 😅

In #102640#1454475, @mano-wii wrote:
Without a crash log and without being able to replicate the problem without having access to the addon it is very difficult for the developer to identify the cause and fix the problem.
It's also not clear if it's a driver issue or if it's exceeded hardware memory limits.

Like I'm saying. The developer was at his wits end and that's why I'm reaching out to you, hoping you can help us to identify the reason why Blender does crash without outputting errors or a crash file.
By the way, you should have access to the addon as it's officially available on Blender Market .

Well, since then I've reinstalled the GPU driver and I also changed from Game Ready to Studio driver but nothing helped. In fact, I don't have any other issues, except this one, neither in Blender or in any other program. In addition, neither the VRAM of the 3090FE or the RAM have reached their limits anytime.

In #102640#1454475, @mano-wii wrote:
In order for us to investigate this issue, please provide a .blend file with simple steps to replicate the issue with the tools available by default in Blender.

I've already attached a .blend file to my second comment but I'll attach it again on this one, too.
However, the developer himself wasn't able to reproduce the issue with this .blend file and he also mentioned that he didn't receive any similar issue reports by his customers.
So, whatever is causing Blender to crash, it currently seems to only happen on my side.

SimpleBakeTest.blend

> In #102640#1454475, @mano-wii wrote: > These messages are common. Many of them are false alerts indicating an incomplete state, which happens when the gpu object is still being configured. > There are plans to clear these messages, but they are highly dependent on the GPU and the order in which the API is called. Okay, thanks for the info. Good to know that those messages are false alerts, so I don't have to be concerned about them 😅 > In #102640#1454475, @mano-wii wrote: > Without a crash log and without being able to replicate the problem without having access to the addon it is very difficult for the developer to identify the cause and fix the problem. > It's also not clear if it's a driver issue or if it's exceeded hardware memory limits. Like I'm saying. The developer was at his wits end and that's why I'm reaching out to you, hoping you can help us to identify the reason why Blender does crash without outputting errors or a crash file. By the way, you should have access to the addon as it's officially available on [Blender Market ](https://blendermarket.com/products/simplebake---simple-pbr-and-other-baking-in-blender-2). Well, since then I've reinstalled the GPU driver and I also changed from Game Ready to Studio driver but nothing helped. In fact, I don't have any other issues, except this one, neither in Blender or in any other program. In addition, neither the VRAM of the 3090FE or the RAM have reached their limits anytime. > In #102640#1454475, @mano-wii wrote: > In order for us to investigate this issue, please provide a .blend file with simple steps to replicate the issue with the tools available by default in Blender. I've already attached a .blend file to my second comment but I'll attach it again on this one, too. However, the developer himself wasn't able to reproduce the issue with this .blend file and he also mentioned that he didn't receive any similar issue reports by his customers. So, whatever is causing Blender to crash, it currently seems to only happen on my side. [SimpleBakeTest.blend](https://archive.blender.org/developer/F13985853/SimpleBakeTest.blend)

Germano Cavalcante commented

2022-12-02 18:14:58 +01:00

In #102640#1454496, @Bango wrote:
(...)
Like I'm saying. The developer was at his wits end and that's why I'm reaching out to you, hoping you can help us to identify the reason why Blender does crash without outputting errors or a crash file.

We do not work with the Simple Bake addon. The problem might be in Cycles, so who would work on this problem would be someone from the #render_cycles team.

In #102640#1454496, @Bango wrote:
(...)
By the way, you should have access to the addon as it's officially available on Blender Market .

Despite the name, Blender Market is not affiliated with the Blender Institute. And even if we had access to the addon, we would still need to simplify the steps before escalating the problem to the developers. (Otherwise they would have to learn to use the addon and simplify it themselves which is a bad use of time).

I think I've seen reports about Simple Bake where the user was successfully able to replicate the issue without using the addon. That helps a lot. (I'm trying to find....)

Perhaps there is no crash log because some software or driver must have forced Blender to close? I've seen this happen with antivirals or with the Windows memory usage security system itself.

To identify the cause of a bug a developer uses a series of software and debuggers. After installing all of them it is also necessary to compile Blender. This can take all day.

For assistance in trying to find the cause of a problem, the crash-log would be a good start but even that is not possible in this case. (Note that this Bug Tracker is for confirming and tracking bugs. For assistance other channels are indicated https:*www.blender.org/community/, https:*wiki.blender.org/wiki/Communication/Contact).

Unfortunately the only practical way to solve this issue is with a developer capable of replicating the problem. If it is not replicable, developers would need to have direct access to the hardware. And even then it is not clear whether it's a solvable problem from Blender side.

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

> In #102640#1454496, @Bango wrote: > (...) > Like I'm saying. The developer was at his wits end and that's why I'm reaching out to you, hoping you can help us to identify the reason why Blender does crash without outputting errors or a crash file. We do not work with the `Simple Bake` addon. The problem might be in Cycles, so who would work on this problem would be someone from the #render_cycles team. > In #102640#1454496, @Bango wrote: > (...) > By the way, you should have access to the addon as it's officially available on [Blender Market ](https://blendermarket.com/products/simplebake---simple-pbr-and-other-baking-in-blender-2). Despite the name, Blender Market is not affiliated with the Blender Institute. And even if we had access to the addon, we would still need to simplify the steps before escalating the problem to the developers. (Otherwise they would have to learn to use the addon and simplify it themselves which is a bad use of time). I think I've seen reports about `Simple Bake` where the user was successfully able to replicate the issue without using the addon. That helps a lot. (I'm trying to find....) Perhaps there is no crash log because some software or driver must have forced Blender to close? I've seen this happen with antivirals or with the Windows memory usage security system itself. To identify the cause of a bug a developer uses a series of software and debuggers. After installing all of them it is also necessary to compile Blender. This can take all day. For assistance in trying to find the cause of a problem, the crash-log would be a good start but even that is not possible in this case. (Note that this Bug Tracker is for confirming and tracking bugs. For assistance other channels are indicated https:*www.blender.org/community/, https:*wiki.blender.org/wiki/Communication/Contact). Unfortunately the only practical way to solve this issue is with a developer capable of replicating the problem. If it is not replicable, developers would need to have direct access to the hardware. And even then it is not clear whether it's a solvable problem from Blender side. Many bugs are fixed between the official releases. Please try the latest development snapshot of blender: https://builder.blender.org/download

David Gonzalez commented

2022-12-02 20:16:05 +01:00

In #102640#1454536, @mano-wii wrote:
We do not work with the Simple Bake addon. The problem might be in Cycles, so who would work on this problem would be someone from the #render_cycles team.

Well, I would really appreciate it. I've just send a bug report via Blender and I directly assumed that someone from the corresponding department would take care of my concern.

Despite the name, Blender Market is not affiliated with the Blender Institute.

I already know that the Blender Foundation isn't responsible for the Blender Market platform, but, to defend myself, I have never claimed that this is the case.

And even if we had access to the addon, we would still need to simplify the steps before escalating the problem to the developers. (Otherwise they would have to learn to use the addon and simplify it themselves which is a bad use of time).

Okay, so what do you guys need to simplify the steps (whatever this means) and to address the issue? I really want to help as best as I can!

I think I've seen reports about Simple Bake where the user was successfully able to replicate the issue without using the addon. That helps a lot. (I'm trying to find....)

Really? This would be very helpful as I then wouldn't be the only one having this issue anymore. Would you then please post the link to this report after you've found it?

Perhaps there is no crash log because some software or driver must have forced Blender to close? I've seen this happen with antivirals or with the Windows memory usage security system itself.

Hmkay well, it definitely would be a painstaking investigation to find out which/if software or driver is forcing Blender to crash. The only antivirus I use is the one that comes with Windows 11. What is the Windows memory usage security system and is there a way to see/find out if there's an issue? Again, VRAM and RAM weren't even close to being utilized during the baking process.

For assistance in trying to find the cause of a problem, the crash-log would be a good start but even that is not possible in this case. (Note that this Bug Tracker is for confirming and tracking bugs. For assistance other channels are indicated https:*www.blender.org/community/, https:*wiki.blender.org/wiki/Communication/Contact).

Okay, but Blender just crashed during usage without hinting any error message or creating a crash file, so I guess this is concern is worth a bug report. This is just my opinion, but I think that Blender should output a crash file, even if another software, driver or anything else has forced Blender to crash.

Unfortunately the only practical way to solve this issue is with a developer capable of replicating the problem. If it is not replicable, developers would need to have direct access to the hardware. And even then it is not clear whether it's a solvable problem from Blender side.

That makes sense and I really hope that someone of the developers will be able to reproduce and finally solve the issue, so that I can continue my work, too.

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

Okay, I guessed that the LTS releases where the most stable versions. That's why I started to use them. Could you please tell me exactly which of the versions you mean? I'll then try it out asap!

> In #102640#1454536, @mano-wii wrote: > We do not work with the `Simple Bake` addon. The problem might be in Cycles, so who would work on this problem would be someone from the #render_cycles team. Well, I would really appreciate it. I've just send a bug report via Blender and I directly assumed that someone from the corresponding department would take care of my concern. > Despite the name, Blender Market is not affiliated with the Blender Institute. I already know that the Blender Foundation isn't responsible for the Blender Market platform, but, to defend myself, I have never claimed that this is the case. >And even if we had access to the addon, we would still need to simplify the steps before escalating the problem to the developers. (Otherwise they would have to learn to use the addon and simplify it themselves which is a bad use of time). Okay, so what do you guys need to simplify the steps (whatever this means) and to address the issue? I really want to help as best as I can! > I think I've seen reports about `Simple Bake` where the user was successfully able to replicate the issue without using the addon. That helps a lot. (I'm trying to find....) Really? This would be very helpful as I then wouldn't be the only one having this issue anymore. Would you then please post the link to this report after you've found it? > Perhaps there is no crash log because some software or driver must have forced Blender to close? I've seen this happen with antivirals or with the Windows memory usage security system itself. Hmkay well, it definitely would be a painstaking investigation to find out which/if software or driver is forcing Blender to crash. The only antivirus I use is the one that comes with Windows 11. What is the Windows memory usage security system and is there a way to see/find out if there's an issue? Again, VRAM and RAM weren't even close to being utilized during the baking process. > For assistance in trying to find the cause of a problem, the crash-log would be a good start but even that is not possible in this case. (Note that this Bug Tracker is for confirming and tracking bugs. For assistance other channels are indicated https:*www.blender.org/community/, https:*wiki.blender.org/wiki/Communication/Contact). Okay, but Blender just crashed during usage without hinting any error message or creating a crash file, so I guess this is concern is worth a bug report. This is just my opinion, but I think that Blender should output a crash file, even if another software, driver or anything else has forced Blender to crash. > Unfortunately the only practical way to solve this issue is with a developer capable of replicating the problem. If it is not replicable, developers would need to have direct access to the hardware. And even then it is not clear whether it's a solvable problem from Blender side. That makes sense and I really hope that someone of the developers will be able to reproduce and finally solve the issue, so that I can continue my work, too. > Many bugs are fixed between the official releases. Please try the latest development snapshot of blender: https://builder.blender.org/download Okay, I guessed that the LTS releases where the most stable versions. That's why I started to use them. Could you please tell me exactly which of the versions you mean? I'll then try it out asap!

David Gonzalez commented

2022-12-07 17:21:44 +01:00

Hey, I would like to know if I still can expect getting help and also a reply from you?

Germano Cavalcante commented

2022-12-07 18:23:14 +01:00

Added subscriber: @brecht

Germano Cavalcante commented

2022-12-07 18:23:14 +01:00

It's hard to tell from the logs if Blender is crashing due to a bug in the code or running out of memory. If you're really looking for a clue as to what causes it, one last thing I'd suggest trying is the --debug-cycles option.
Run ./blender.exe --debug-cycles > cycles_debug_log.txt from the command line, trigger the bug, and attach the resulting file here.
https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html

I talked to @brecht and he suggested a few ways you can try to give us some info:

Isolate which pass exactly is crashing when using SimpleBake, by disabling baking of passes and simplifying the shader node setup until you find the problematic one. And from that information create a .blend file to reproduce the problem without SimpleBake.
The developer of the add-on should be able to isolate exactly which bake operation crashes Blender or which pass and object. So they can also provide us with more information.
Share the add-on with Blender developers. Blender Market says it's GPL licensed so this should be allowed.

Note that the provided .blend file contains a very complicated shader node graph and custom node groups. It's important to make some effort to simplify this and perhaps find out that something specific is causing the problem.

Could this crash be related to some other add-on? Maybe the SimpleBake's developer couldn't replicate it because they didn't have this add-on?

It's hard to tell from the logs if Blender is crashing due to a bug in the code or running out of memory. If you're really looking for a clue as to what causes it, one last thing I'd suggest trying is the `--debug-cycles` option. Run `./blender.exe --debug-cycles > cycles_debug_log.txt` from the command line, trigger the bug, and attach the resulting file here. https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html I talked to @brecht and he suggested a few ways you can try to give us some info: - Isolate which pass exactly is crashing when using `SimpleBake`, by disabling baking of passes and simplifying the shader node setup until you find the problematic one. And from that information create a .blend file to reproduce the problem without `SimpleBake`. - The developer of the add-on should be able to isolate exactly which bake operation crashes Blender or which pass and object. So they can also provide us with more information. - Share the add-on with Blender developers. Blender Market says it's GPL licensed so this should be allowed. Note that the provided .blend file contains a very complicated shader node graph and custom node groups. It's important to make some effort to simplify this and perhaps find out that something specific is causing the problem. Could this crash be related to some other add-on? Maybe the SimpleBake's developer couldn't replicate it because they didn't have this add-on?

David Gonzalez commented

2022-12-07 20:48:11 +01:00

Thanks for coming back!

https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html

This is for Linux. I'm using Windows 11 ;)
However, I were able to open Blender with the debug cycles option trough the windows console with the line you've posted, I just had to delete the "./" at the beginning.
Here is the created log file:
blender_cycles_debug_log.txt

I talked to @brecht and he suggested a few ways you can try to give us some info:

Isolate which pass exactly is crashing when using SimpleBake, by disabling baking of passes and simplifying the shader node setup until you find the problematic one. And from that information create a .blend file to reproduce the problem without SimpleBake.

Hmkay, I don't really know if I understand what I've to do but I'll try my best. With "pass" you mean shader input node like diffuse etc. or?

The developer of the add-on should be able to isolate exactly which bake operation crashes Blender or which pass and object. So they can also provide us with more information.

Share the add-on with Blender developers. Blender Market says it's GPL licensed so this should be allowed.

Well, if the developer doesn't mind and if this helps to identify the issue I could share the addon with you but I don't want to attach the addon here as this bug report seems to be public and so everyone would be able download it, what I dislike.
But maybe I can persuade the developer to join this task and maybe he is willed to provide you with a copy of his addon.

Note that the provided .blend file contains a very complicated shader node graph and custom node groups. It's important to make some effort to simplify this and perhaps find out that something specific is causing the problem.

Yes, the contained material is very complex but I were already able to ensure that this material wasn't responsible for the crash as it also happened when I tried to bake with a simple material setup with only a color input.

Could this crash be related to some other add-on? Maybe the SimpleBake's developer couldn't replicate it because they didn't have this add-on?

The developer already had this thought, too, but I wasn't able to find out which one it could be.

I'm going to reach out to the developer and I'll ask him to join this task. Hopefully, if he agrees, we then can identify and solve the issue together.
In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output.
I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled.
If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash.

Thanks for coming back! > https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html This is for Linux. I'm using Windows 11 ;) However, I were able to open Blender with the debug cycles option trough the windows console with the line you've posted, I just had to delete the "./" at the beginning. Here is the created log file: [blender_cycles_debug_log.txt](https://archive.blender.org/developer/F14019209/blender_cycles_debug_log.txt) > I talked to @brecht and he suggested a few ways you can try to give us some info: > > - Isolate which pass exactly is crashing when using `SimpleBake`, by disabling baking of passes and simplifying the shader node setup until you find the problematic one. And from that information create a .blend file to reproduce the problem without `SimpleBake`. Hmkay, I don't really know if I understand what I've to do but I'll try my best. With "pass" you mean shader input node like diffuse etc. or? > - The developer of the add-on should be able to isolate exactly which bake operation crashes Blender or which pass and object. So they can also provide us with more information. > - Share the add-on with Blender developers. Blender Market says it's GPL licensed so this should be allowed. Well, if the developer doesn't mind and if this helps to identify the issue I could share the addon with you but I don't want to attach the addon here as this bug report seems to be public and so everyone would be able download it, what I dislike. But maybe I can persuade the developer to join this task and maybe he is willed to provide you with a copy of his addon. > Note that the provided .blend file contains a very complicated shader node graph and custom node groups. It's important to make some effort to simplify this and perhaps find out that something specific is causing the problem. Yes, the contained material is very complex but I were already able to ensure that this material wasn't responsible for the crash as it also happened when I tried to bake with a simple material setup with only a color input. > Could this crash be related to some other add-on? Maybe the SimpleBake's developer couldn't replicate it because they didn't have this add-on? The developer already had this thought, too, but I wasn't able to find out which one it could be. I'm going to reach out to the developer and I'll ask him to join this task. Hopefully, if he agrees, we then can identify and solve the issue together. In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output. I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled. If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash.

Lewis Toohey commented

2022-12-08 16:13:08 +01:00

Added subscriber: @lewis2e

Lewis Toohey commented

2022-12-08 16:13:08 +01:00

I am the developer of SimpleBake. I am providing a copy of the addon here in case it can help diagnose this problem (minus the auto-update capability, which will not be relevant).

For my part, I would say

I have never been able to reproduce this user’s problem myself. They sent me a blend file and it baked just fine. I have the user’s report, but no direct evidence myself that this problem exists.
I have had no other users report this issue (for context, almost 6000 copies sold).

In allother cases of a SimpleBake problem, I have had some kind of error message to work with (either a traceback at the level of the Python script, or a “deeper” error from Blender). That seemingly doesn’t happen in this user’s case. Apparently there is no error message at all.

That last point is why I suspect this might be Blender problem rather than a SimpleBake problem, but I could not say that for certain.

If sharing SimpleBake for testing helps reveal a problem, then great - but I have reached the end of what I can do.

I am the developer of SimpleBake. I am providing a copy of the addon here in case it can help diagnose this problem (minus the auto-update capability, which will not be relevant). For my part, I would say - I have never been able to reproduce this user’s problem myself. They sent me a blend file and it baked just fine. I have the user’s report, but no direct evidence myself that this problem exists. - I have had no other users report this issue (for context, almost 6000 copies sold). # In **all**other cases of a SimpleBake problem, I have had some kind of error message to work with (either a traceback at the level of the Python script, or a “deeper” error from Blender). That seemingly doesn’t happen in this user’s case. Apparently there is no error message at all. That last point is why I suspect this might be Blender problem rather than a SimpleBake problem, but I could not say that for certain. If sharing SimpleBake for testing helps reveal a problem, then great - but I have reached the end of what I can do.

Brecht Van Lommel commented

2022-12-08 17:02:21 +01:00

I'm unable to reproduce the crash with the add-on also.

In #102640#1456314, @Bango wrote:

https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html

This is for Linux. I'm using Windows 11 ;)
However, I were able to open Blender with the debug cycles option trough the windows console with the line you've posted, I just had to delete the "./" at the beginning.
Here is the created log file:
blender_cycles_debug_log.txt

This log doesn't show a crash unfortunately. It shows two 4096x4096x bakes that were completed, and two 32x32 icon preview renders that also completed. The logs in the original description also show no message indicating a crash.

Just to be clear, when you say it crashes, is there some Windows popup saying Blender crashed? Or does Blender close without any message? It's possible that for some reason Blender exited when it shouldn't, but without crashing.

In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output.
I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled.
If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash.

Yes, I think at this point the most important thing is trying to isolate the cause.

I'm unable to reproduce the crash with the add-on also. > In #102640#1456314, @Bango wrote: >> https://docs.blender.org/manual/en/latest/advanced/command_line/launch/linux.html > This is for Linux. I'm using Windows 11 ;) > However, I were able to open Blender with the debug cycles option trough the windows console with the line you've posted, I just had to delete the "./" at the beginning. > Here is the created log file: > [blender_cycles_debug_log.txt](https://archive.blender.org/developer/F14019209/blender_cycles_debug_log.txt) This log doesn't show a crash unfortunately. It shows two 4096x4096x bakes that were completed, and two 32x32 icon preview renders that also completed. The logs in the original description also show no message indicating a crash. Just to be clear, when you say it crashes, is there some Windows popup saying Blender crashed? Or does Blender close without any message? It's possible that for some reason Blender exited when it shouldn't, but without crashing. > In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output. > I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled. > If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash. Yes, I think at this point the most important thing is trying to isolate the cause.

David Gonzalez commented

2022-12-08 18:06:08 +01:00

First of all I want to thank @lewis2e for participating here and for providing us with a version of his addon to help me finding the issue!

In #102640#1456936, @brecht wrote:
This log doesn't show a crash unfortunately. It shows two 4096x4096x bakes that were completed, and two 32x32 icon preview renders that also completed. The logs in the original description also show no message indicating a crash.

Just to be clear, when you say it crashes, is there some Windows popup saying Blender crashed? Or does Blender close without any message? It's possible that for some reason Blender exited when it shouldn't, but without crashing.

No, there's no Windows popup or anything else showing a message when Blender crashes. Blender just closes and that's it. That's the weird thing about it! Blender doesn't show anything, neither does Blender show any message internal nor does it show any related error in one of the log files and it also doesn't create any crash file, otherwise we could identify better what is causing the crash. I have to admit that the baking process didn't force Blender to crash in 2 of 10 cases but in one of those successful bakes I just got blank images.

In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output.
I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled.
If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash.

Yes, I think at this point the most important thing is trying to isolate the cause.

So I created a new test.blend file but this time I couldn't trigger the crash and I were able to bake with every possible workflow Simple Bake offers without any issue. I then tried another run on the .blend file where the issue appeared the first time and this time I were able to bake the asset without any crash, too, but here I only tried one of the possible workflows of Simple Bake for now. I'll have to do some more tests in which I'm going to check the other workflows.

Ah, and I'm still using the Blender 3.3.1 version with all addons enabled.

First of all I want to thank @lewis2e for participating here and for providing us with a version of his addon to help me finding the issue! > In #102640#1456936, @brecht wrote: > This log doesn't show a crash unfortunately. It shows two 4096x4096x bakes that were completed, and two 32x32 icon preview renders that also completed. The logs in the original description also show no message indicating a crash. > > Just to be clear, when you say it crashes, is there some Windows popup saying Blender crashed? Or does Blender close without any message? It's possible that for some reason Blender exited when it shouldn't, but without crashing. No, there's no Windows popup or anything else showing a message when Blender crashes. Blender just closes and that's it. That's the weird thing about it! Blender doesn't show anything, neither does Blender show any message internal nor does it show any related error in one of the log files and it also doesn't create any crash file, otherwise we could identify better what is causing the crash. I have to admit that the baking process didn't force Blender to crash in 2 of 10 cases but in one of those successful bakes I just got blank images. >> In addition I'm going to create a new and more suitable .blend file with more than one object, each with a different but simple color output. >> I'll then again to some tests with the current Blender version I use, Blender 3.3.1 LTS version which I've downloaded from the Microsoft store, and with all addons enabled. >> If Blender still crashes I'll then try some tests with the portal version of the latest Blender 3.4 build that's marked as stable, but this time I'll only enable Simple Bake from the beginning and then I'll try to identify if one of the other addons is causing the crash. > > Yes, I think at this point the most important thing is trying to isolate the cause. So I created a new test.blend file but this time I couldn't trigger the crash and I were able to bake with every possible workflow Simple Bake offers without any issue. I then tried another run on the .blend file where the issue appeared the first time and this time I were able to bake the asset without any crash, too, but here I only tried one of the possible workflows of Simple Bake for now. I'll have to do some more tests in which I'm going to check the other workflows. Ah, and I'm still using the Blender 3.3.1 version with all addons enabled.

Lewis Toohey commented

2022-12-08 20:06:24 +01:00

Removed subscriber: @lewis2e

David Gonzalez commented

2022-12-10 16:46:59 +01:00

I did several tests since last time and Blender didn't crash a single time by now. I can't say what has fixed the issue but gladly it's gone. The only changes during the last days, which, as far as I can say, could probably be decisive for solving the issue, were updates for Simple Bake and the Python 3.10 runtime. The former I could easily check as I still have an older version of Simple Bake but the issue still didn't reappear so I guess it was related to the Python runtime or maybe something else. However, it's gone now, so there's no reason to keep this task open anymore.

Thanks to everyone who participated in this conversation and who tried to help! ✌️

I did several tests since last time and Blender didn't crash a single time by now. I can't say what has fixed the issue but gladly it's gone. The only changes during the last days, which, as far as I can say, could probably be decisive for solving the issue, were updates for Simple Bake and the Python 3.10 runtime. The former I could easily check as I still have an older version of Simple Bake but the issue still didn't reappear so I guess it was related to the Python runtime or maybe something else. However, it's gone now, so there's no reason to keep this task open anymore. Thanks to everyone who participated in this conversation and who tried to help! ✌️

Germano Cavalcante commented

2022-12-12 13:18:48 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Germano Cavalcante closed this issue

2022-12-12 13:18:48 +01:00

Germano Cavalcante commented

2022-12-12 13:18:48 +01:00

Good to see that the problem is no longer happening for you.

Unfortunately we were not able to determine what caused it.

If the problem bothers you again, feel free to open a new report following the submission template and guidelines (It says, for example, to "Find steps to redo the bug consistently without any non-official add-ons").

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Good to see that the problem is no longer happening for you. Unfortunately we were not able to determine what caused it. If the problem bothers you again, feel free to open a new report following the [submission template and guidelines](https://developer.blender.org/maniphest/task/edit/form/1/) (It says, for example, to "Find steps to redo the bug consistently without any non-official add-ons"). A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender crashes during baking process #102640

In allother cases of a SimpleBake problem, I have had some kind of error message to work with (either a traceback at the level of the Python script, or a “deeper” error from Blender). That seemingly doesn’t happen in this user’s case. Apparently there is no error message at all.