Blender crashes after GPU spike (Specially when we have a character with Rigify) #103461

New Issue

Adolfo · 2022-12-25T05:27:45+01:00

Adolfo commented

2022-12-25 05:27:45 +01:00

System Information
Operating system: Windows 10
Graphics card: RTX 2070 Super

Blender Version
Broken: 3.4.1
Worked: 3.3

Every time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve.

Exact steps for others to reproduce the error

Open a blender file
Import a character using rigfy with Linked Library
Library override
Turn Eeve on
Start working
Eventually, blender will crash.

I noticed that if I don't import a character with rigfy, it doesn't have the GPU spike
Christmas.crash.txt
KalyAndAkrasiel 3.5.crash.txt

**System Information** Operating system: Windows 10 Graphics card: RTX 2070 Super **Blender Version** Broken: 3.4.1 Worked: 3.3 Every time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve. **Exact steps for others to reproduce the error** - Open a blender file - Import a character using rigfy with Linked Library - Library override - Turn Eeve on - Start working - Eventually, blender will crash. I noticed that if I don't import a character with rigfy, it doesn't have the GPU spike [Christmas.crash.txt](https://archive.blender.org/developer/F14091742/Christmas.crash.txt) [KalyAndAkrasiel 3.5.crash.txt](https://archive.blender.org/developer/F14091747/KalyAndAkrasiel_3.5.crash.txt)

Adolfo commented

2022-12-25 05:27:45 +01:00

Added subscriber: @Corintio

Pratik Borhade commented

2022-12-25 11:33:02 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-12-25 11:33:02 +01:00

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

Pratik Borhade commented

2022-12-25 11:33:03 +01:00

Hi, thanks for the report. Could you share a file which consists an object you're linking in another file?
Please also attach crash logs:

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 report. Could you share a file which consists an object you're linking in another file? Please also attach crash logs: > 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)

Adolfo commented

2022-12-25 13:12:42 +01:00

The crash files are these ones here:
Christmas.crash.txt KalyAndAkrasiel 3.5.crash.txt

And they all used this rig here that never really caused problems before version 3.4:
https://1drv.ms/u/s!AtoroRr-loi_kOI3LyFbFIsUOznadw?e=06F8YI

When I link the main character on another file and then move things around too much, especially while previewing in Eeve, it crashes. It happens more when I have two characters in the same scene too. It didn't happen before this blender version, these spikes on the GPU cause things to crash. And I have tested rolling back to blender 3.3 and linking characters from this same file, and working, and I have no issues.

The crash files are these ones here: [Christmas.crash.txt](https://archive.blender.org/developer/F14091742/Christmas.crash.txt) [KalyAndAkrasiel 3.5.crash.txt](https://archive.blender.org/developer/F14091747/KalyAndAkrasiel_3.5.crash.txt) And they all used this rig here that never really caused problems before version 3.4: https://1drv.ms/u/s!AtoroRr-loi_kOI3LyFbFIsUOznadw?e=06F8YI When I link the main character on another file and then move things around too much, especially while previewing in Eeve, it crashes. It happens more when I have two characters in the same scene too. It didn't happen before this blender version, these spikes on the GPU cause things to crash. And I have tested rolling back to blender 3.3 and linking characters from this same file, and working, and I have no issues.

Pratik Borhade commented

2022-12-26 03:29:27 +01:00

Thanks for the info. Reference file you've attached is quite large (~2GB). Could you upload simplified version or other smaller file which would cause the crash?

Adolfo commented

2022-12-26 08:50:40 +01:00

In #103461#1465724, @PratikPB2123 wrote:
Thanks for the info. The reference file you've attached is quite large (~2GB). Could you upload simplified version or other smaller file which would cause the crash?

Hello! I unpacked the textures to split it in half. So now the actual rig is 627mb and the texture folder is 1,5gb
So you can get the file here: https://1drv.ms/u/s!AtoroRr-loi_kOJCr2bOAKn52ArZ0w?e=zt08lj
And if needed, the textures here: https://1drv.ms/u/s!AtoroRr-loi_kOJD0mLsDH6-4NLk3g?e=CkYhsv

> In #103461#1465724, @PratikPB2123 wrote: > Thanks for the info. The reference file you've attached is quite large (~2GB). Could you upload simplified version or other smaller file which would cause the crash? Hello! I unpacked the textures to split it in half. So now the actual rig is 627mb and the texture folder is 1,5gb So you can get the file here: https://1drv.ms/u/s!AtoroRr-loi_kOJCr2bOAKn52ArZ0w?e=zt08lj And if needed, the textures here: https://1drv.ms/u/s!AtoroRr-loi_kOJD0mLsDH6-4NLk3g?e=CkYhsv

Pratik Borhade commented

2022-12-26 10:39:58 +01:00

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

Richard Antalik commented

2023-01-05 10:05:58 +01:00

Added subscriber: @iss

Richard Antalik commented

2023-01-05 10:05:58 +01:00

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

Richard Antalik commented

2023-01-05 10:05:58 +01:00

@Corintio Looking at steps to reproduce, with provided file it seems that relevant step would be "Start working". This is very vague. Can you provide steps to cause the crash? if you can't provide exact steps, provide as much details as you can.

Also check if this issue happens with alpha build from https://builder.blender.org/download/daily/.

@Corintio Looking at steps to reproduce, with provided file it seems that relevant step would be "Start working". This is very vague. Can you provide steps to cause the crash? if you can't provide exact steps, provide as much details as you can. Also check if this issue happens with alpha build from https://builder.blender.org/download/daily/.

Adolfo commented

2023-01-05 20:58:19 +01:00

In #103461#1469491, @iss wrote:
@Corintio Looking at steps to reproduce, with provided file it seems that relevant step would be "Start working". This is very vague. Can you provide steps to cause the crash? if you can't provide exact steps, provide as much details as you can.

Also check if this issue happens with alpha build from https://builder.blender.org/download/daily/.

Oh sorry, start working I mean that I added a scene with some lights and then was trying to pose the character. If I'm posing on EEVE it crashes really fast, if I'm not using EEVE or have the simplify options turned on, it takes longer to crash. Usually it takes a few minutes until the first crash happens, then after the first, every 30 seconds of posing the character and moving things around crashes and I can no longer work.
This issue did not happen in version 3.3, the GPU spikes began in 3.4. And I tried opening the file in 3.3 to double-check if it was something on my side and despite the materials breaking because of nodes that are not retrocompatible, blender never crashes like this.

> In #103461#1469491, @iss wrote: > @Corintio Looking at steps to reproduce, with provided file it seems that relevant step would be "Start working". This is very vague. Can you provide steps to cause the crash? if you can't provide exact steps, provide as much details as you can. > > Also check if this issue happens with alpha build from https://builder.blender.org/download/daily/. Oh sorry, start working I mean that I added a scene with some lights and then was trying to pose the character. If I'm posing on EEVE it crashes really fast, if I'm not using EEVE or have the simplify options turned on, it takes longer to crash. Usually it takes a few minutes until the first crash happens, then after the first, every 30 seconds of posing the character and moving things around crashes and I can no longer work. This issue did not happen in version 3.3, the GPU spikes began in 3.4. And I tried opening the file in 3.3 to double-check if it was something on my side and despite the materials breaking because of nodes that are not retrocompatible, blender never crashes like this.

Richard Antalik commented

2023-01-06 13:23:36 +01:00

This is not quite what I meant, we need exact steps to reproduce the issue, this pretty much means to describe every single operation.
I have tried to move some bones for a few minutes, but no crash happened. Since the crash is related to overrides, I don't think I need textures, but please check if this is correct.

This is not quite what I meant, we need exact steps to reproduce the issue, this pretty much means to describe every single operation. I have tried to move some bones for a few minutes, but no crash happened. Since the crash is related to overrides, I don't think I need textures, but please check if this is correct.

Adolfo commented

2023-01-13 23:00:00 +01:00

In #103461#1470142, @iss wrote:
This is not quite what I meant, we need exact steps to reproduce the issue, this pretty much means to describe every single operation.
I have tried to move some bones for a few minutes, but no crash happened. Since the crash is related to overrides, I don't think I need textures, but please check if this is correct.

Get a blender scene with some objects and materials already set to work on Eeve
Link the collection Kalyskah
Library override
Make some poses
Eventually, it will crash

Now it's awkward that I'm trying to replicate the issue, but I'm also not having it anymore. And this issue was consistent for weeks until I reported it. So I'm starting to suspect it could have been an issue with my Nvidea driver and once GeForce experience was updated, it fixed.
The strange part is that even if it was an issue with the driver, blender 3.3 was still working.

> In #103461#1470142, @iss wrote: > This is not quite what I meant, we need exact steps to reproduce the issue, this pretty much means to describe every single operation. > I have tried to move some bones for a few minutes, but no crash happened. Since the crash is related to overrides, I don't think I need textures, but please check if this is correct. - Get a blender scene with some objects and materials already set to work on Eeve - Link the collection Kalyskah - Library override - Make some poses - Eventually, it will crash Now it's awkward that I'm trying to replicate the issue, but I'm also not having it anymore. And this issue was consistent for weeks until I reported it. So I'm starting to suspect it could have been an issue with my Nvidea driver and once GeForce experience was updated, it fixed. The strange part is that even if it was an issue with the driver, blender 3.3 was still working.

Richard Antalik commented

2023-01-16 21:59:32 +01:00

We do change how GPU is used to draw things, so it is possible, that there was bug in driver, or sometimes new driver will result in new bug. But from crash trace, I would not think, that this was the issue in this case.

Also I should have clarified even more, for developer to fix a bug, it is not possible to attempt to reproduce the issue for a long time. Sometimes it takes many attempts to trace the cause. So if issue can't be reproduced in few minutes at most, it may not be considered as "worth fixing", depending on other work that has to be done.

Do you still work with this file? If so will you leave a comment if the crash will happen again?

We do change how GPU is used to draw things, so it is possible, that there was bug in driver, or sometimes new driver will result in new bug. But from crash trace, I would not think, that this was the issue in this case. Also I should have clarified even more, for developer to fix a bug, it is not possible to attempt to reproduce the issue for a long time. Sometimes it takes many attempts to trace the cause. So if issue can't be reproduced in few minutes at most, it may not be considered as "worth fixing", depending on other work that has to be done. Do you still work with this file? If so will you leave a comment if the crash will happen again?

Adolfo commented

2023-01-17 17:07:09 +01:00

In #103461#1475168, @iss wrote:
We do change how GPU is used to draw things, so it is possible, that there was bug in driver, or sometimes new driver will result in new bug. But from crash trace, I would not think, that this was the issue in this case.

Also I should have clarified even more, for developer to fix a bug, it is not possible to attempt to reproduce the issue for a long time. Sometimes it takes many attempts to trace the cause. So if issue can't be reproduced in few minutes at most, it may not be considered as "worth fixing", depending on other work that has to be done.

Do you still work with this file? If so will you leave a comment if the crash will happen again?

I understand it. And yes, I do work with this file just not at this moment. I'm just finishing some other work and at the beginning of the next month I'll have more animations to work on and will work on it again, I'll message here if the problem still happens, thanks!

> In #103461#1475168, @iss wrote: > We do change how GPU is used to draw things, so it is possible, that there was bug in driver, or sometimes new driver will result in new bug. But from crash trace, I would not think, that this was the issue in this case. > > Also I should have clarified even more, for developer to fix a bug, it is not possible to attempt to reproduce the issue for a long time. Sometimes it takes many attempts to trace the cause. So if issue can't be reproduced in few minutes at most, it may not be considered as "worth fixing", depending on other work that has to be done. > > Do you still work with this file? If so will you leave a comment if the crash will happen again? I understand it. And yes, I do work with this file just not at this moment. I'm just finishing some other work and at the beginning of the next month I'll have more animations to work on and will work on it again, I'll message here if the problem still happens, thanks!

Richard Antalik commented

2023-01-17 18:37:43 +01:00

Thanks for info. Will keep report in needs info status for now so I won't forget about this.

Adolfo commented

2023-01-26 00:53:21 +01:00

In #103461#1475643, @iss wrote:
Thanks for info. Will keep report in needs info status for now so I won't forget about this.

I'm getting the crashes again. This time I realised that after an hour of working, now every time I move too much the fingers of the characters, Blender crashes.

> In #103461#1475643, @iss wrote: > Thanks for info. Will keep report in needs info status for now so I won't forget about this. I'm getting the crashes again. This time I realised that after an hour of working, now every time I move too much the fingers of the characters, Blender crashes.

Adolfo commented

2023-01-26 01:12:13 +01:00

And I just tested here, rewinding to version 3.3 and I can work on the same file without having these crashes

Richard Antalik commented

2023-01-31 02:26:01 +01:00

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

Richard Antalik commented

2023-01-31 02:26:01 +01:00

Thanks for update, I am not sure how to get to reproducible cse at this point, so will leave open.

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 after GPU spike (Specially when we have a character with Rigify) #103461