Blender crashes when closing #113
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/test#113
Reference in New Issue
Block a user
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?
Original bug report: https://projects.blender.org/blender/blender/issues/157178
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 591.86 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: (newest version of Blender that worked as expected)
Short description of error
Blender crashes when closing program
Exact steps for others to reproduce the error
Open blender 5.1.0, and without any more steps just simply close app using the cross in the upper right corner, get an error
(I added an error message I get)
This bug only appears in latest version 5.1.0
I tried reinstalling Blender but this doesnt help
Report is clear
LLM Reasoning
Got it, let's see. The question is whether the bug report clearly describes the issue. First, check the clarity of the text and steps to reproduce.
The title says "Blender crashes when closing". The body has a short description: "Blender crashes when closing program". Then the exact steps: "Open blender 5.1.0, and without any more steps just simply close app using the cross in the upper right corner, get an error".
So the issue is clearly stated (crash on closing), and the steps to reproduce are simple and clear. Even though there's system info, we ignore that. The description is straightforward. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 8.430638
}
Report is specific
LLM Reasoning
Got it, let's analyze the bug report. The title is "Blender crashes when closing", and the body describes that Blender crashes specifically when closing the program using the cross button. The exact steps are given: open Blender 5.1.0 and close with the cross. It also mentions this only happens in version 5.1.0. So it's a specific issue because it's about a particular action (closing) leading to a crash, not a vague rendering crash or something general. Wait, but let's check the definitions. Specific is about a specific feature or step. The steps are exact: open and close with cross. So yes, it's specific. But wait, the example for generic was "Crashing while rendering" (vague), and specific was "Crashing while using a specific feature while rendering". Here, the action is closing, which is a specific step. So the answer should be Specific? Wait, but let me recheck. The bug report says "Blender crashes when closing program" with exact steps: open and close with cross. That's a specific issue because it's tied to a particular action (closing) in a specific way. So the answer is Specific.
JSON Data
{
"llm_judgement": true,
"processing_time": 13.602881000000002
}
Report flagged as NOT a duplicate by LLM
Blender crashes every time I try to close it
https://projects.blender.org/blender/blender/issues/156152
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 565.90 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: 5.0
Short description of error
Blender crashes every time when I try to close it or when I press "load factory settings".
Exact steps for others to reproduce the error
Press the close button (windows frame) or press File - Defaults - Load factory settings.
Attached .blend file.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps to reproduce.
Bug report 1: Crashes when closing the program by clicking the cross in the upper right corner. Steps are just opening Blender 5.1.0 and closing it.
Bug report 2: Crashes every time when trying to close (same as report 1) or when pressing "load factory settings". So steps include closing via window frame or load factory settings.
The key here is that both mention crashes on closing, but report 2 adds another trigger (load factory settings). However, the main issue of crashing on close is present in both. Wait, but let's check if they are the same. The first one's steps are just closing, the second includes closing and load factory. But maybe the core issue is the crash on close. Let's see the versions: both use 5.1.0. System info: different GPUs (3090 vs 3060) but same OS.
Wait, the question is if they are the same issue. The first report's error is "crashes when closing", steps are open and close. Second report's error is "crashes every time I try to close it or load factory settings". So the closing part is common. But does the second report's additional trigger (load factory) make them different? Or is the core issue the crash on close, so they might be duplicates?
Wait, let's check the steps. Report 1: open, close via cross. Report 2: close via window frame or load factory. So both have closing as a step. The difference is report 2 has an extra step (load factory). But maybe the underlying issue is the same—crash on close. Let's see if the descriptions are similar. Both say Blender crashes when closing. The second one adds another scenario, but the main issue of crashing on close is shared.
But wait, the question is to focus on Description and Steps. Let's list:
Report 1 Description: "Blender crashes when closing program" — steps: open, close via cross.
Report 2 Description: "Blender crashes every time when I try to close it or when I press 'load factory settings'" — steps: close via window frame OR load factory.
So the common part is crashing on close. The second report has an additional trigger, but maybe that's a separate issue? Or is it part of the same bug?
Wait, maybe the answer is Yes because both are about crashing when closing. Let's see. The first report's steps are just closing, the second includes closing and another action. But if the core issue is the crash on close, then they might be duplicates. Alternatively, if the load factory is a different trigger, but maybe it's related.
Alternatively, maybe No because report 2 has an extra step (load factory) which isn't in report 1. Let's think: if two reports have the same main issue (crash on close) even with an additional step, are they duplicates? Maybe yes, because the primary issue is the crash on close. The load factory might be a separate but related bug, but the question is if they are the same issue.
Wait, let's check the versions: both use 5.1.0. So maybe the same underlying problem. Let's see the steps: report 1's step is closing via cross, report 2's step is closing via window frame (same as cross) or load factory. So the closing part is identical. The load factory is an extra, but maybe that's a different symptom of the same bug.
So based on the description and steps, both are about crashing when closing. So they might be duplicates. Therefore, answer Yes? Wait, no—wait report 2 has two triggers: close or load factory. Report 1 only has close. But if the main issue is crash on close, then maybe yes. Alternatively, maybe No because report 2 has an additional trigger.
Wait, let's re-examine. The question says "focus primarily on the 'Description of issue' and 'Steps to reproduce the issue' section."
Report 1 Description: crashes when closing program. Steps: open, close via cross.
Report 2 Description: crashes every time when trying to close it or load factory settings. Steps: close via window frame OR load factory.
So the description of report 2 includes "or load factory", which is not in report 1. The steps for report 2 include two scenarios, one of which (close) matches report 1's step. But does that make them the same issue? If the core issue is crash on close, then yes. But if the load factory is a separate bug, then no.
But maybe the answer is Yes because both are about crashing when closing. Let's see: the first report's error is "crashes when closing", second is "crashes every time I try to close it". So that's the same. The load factory is an extra, but maybe that's part of the same bug. Alternatively, maybe No because report 2 has an additional step.
Wait, let's think of duplicates: if two reports describe the same problem with the same steps (or similar), they are duplicates. Report 1's step is open and close via cross. Report 2's step includes closing via window frame (same as cross) or load factory. So the closing part is the same. The load factory is an extra, but maybe that's a different issue. But the question is if they are the same issue.
Alternatively, maybe No because report 2 has an additional trigger. Let's check the system info: different GPUs (3090 vs 3060), but same OS and Blender version. So maybe the bug is related to closing, regardless of GPU.
Hmm. Maybe the answer is Yes, because both are about crashing when closing. The load factory in report 2 might be a separate symptom, but the main issue is crash on close. So they are duplicates. Therefore, answer Yes? Wait, no—wait, let's see: if two reports have different steps (one has only close, another has close and load factory), then maybe not. But maybe the core issue is the same.
Alternatively, maybe No because report 2 includes an additional step that report 1 doesn't have. So they are not the same. Let's think again. The first report's steps: open, close via cross. Second report's steps: close via window frame OR load factory. So the second report has two ways to reproduce, one of which is closing (same as first), but the other is different. So if the issue is crash on close, then both have that. But if the load factory is a separate bug, then they are not the same.
But the question is whether they are the same issue. Let's see: report 1 says "crashes when closing program" — steps: open and close. Report 2 says "crashes every time when I try to close it or load factory settings" — steps: close OR load factory. So the common part is crash on close. The difference is report 2 has an extra trigger. But maybe that's a different bug, so they are not the same. Therefore, answer No? Wait, but maybe the load factory is related to closing (like when loading factory settings, it closes or something). Not sure.
Alternatively, let's check the error messages: both mention crashing on close. So maybe Yes. But I'm confused. Let's go with the main issue: both are about crashing when closing. So answer Yes? Or No?
Wait, the user says "if you are unsure, then respond 'No'". Maybe I should say No because report 2 has an additional step (load factory) that report 1 doesn't have. So they are not the same. Therefore, answer No.
JSON Data
{
"llm_judgement": false,
"processing_time": 83.456361,
"duplicate_report_number": "156152"
}
Report flagged as duplicate by LLM
Blender crash when closing.
https://projects.blender.org/blender/blender/issues/157091
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5070 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.03 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: (newest version of Blender that worked as expected)
Short description of error
I can create a project and save it, but when I close Blender, it crashes.
Exact steps for others to reproduce the error
Open and exit Blender
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce.
Bug report 1: Description is "Blender crashes when closing program". Steps: Open blender 5.1.0, close with cross in upper right corner, get error.
Bug report 2: Description is "I can create a project and save it, but when I close Blender, it crashes." Steps: Open and exit Blender.
Both are about Blender crashing when closing. The steps are similar (open then close). The descriptions both mention crash on closing. Even though the system info has different OS and GPU, the core issue is the same—crash on closing. So they are duplicates.
JSON Data
{
"llm_judgement": true,
"processing_time": 9.714922,
"duplicate_report_number": "157091"
}
Report flagged as duplicate by LLM
Closing Blender 5.1 crashes Blender 5.1 with a crash warning.
https://projects.blender.org/blender/blender/issues/155812
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 NVIDIA Corporation NVIDIA 591.74 Vulkan Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: Blender 5.0.2
Short description of error
Closing Blender 5.1 crashes Blender 5.1. Even an empty blend file. Blender gives me the crash warning and crash log which is attached.
Exact steps for others to reproduce the error
To be honest, i don't know. Even opening and closing an empty blend file is crashing blender 5.1 for me. it might be becasue of some old addon but i'm too stupid to figure out which or how.
Really appreciate the help. Thank you!
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to Reproduce.
Bug Report 1:
Bug Report 2:
Both are about Blender crashing when closing, same version (5.1.0), similar steps (closing the app). The core issue is the crash on close. Even though Report 2 mentions a possible addon, the main problem is the same: closing Blender causes a crash. So they seem to be duplicates.
JSON Data
{
"llm_judgement": true,
"processing_time": 11.961582,
"duplicate_report_number": "155812"
}
Report flagged as duplicate by LLM
Blender crashes most of the time when closing.
https://projects.blender.org/blender/blender/issues/155870
System Information
Operating system: Windows-11-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080 NVIDIA Corporation NVIDIA 580.97 Vulkan Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: (newest version of Blender that worked as expected)
Short description of error
[Please fill out a short description of the error here]
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]
Blender crashes most of the time when closing. All the addons are up to date. Was doing on 5.01. Now doing on 5.1
Crash report added.
5.1 is nice. Crash at end not affecting anything but i do get the crash window when closing.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the key sections: Description and Steps to reproduce.
Bug report 1 says Blender crashes when closing, steps are open 5.1.0 and close with the X button. Bug report 2 also mentions crashing most of the time when closing, and they're using 5.1.0 too. Both have similar symptoms (crash on closing) and same Blender version. The steps might be slightly different but the core issue is closing causing a crash. So are they duplicates? Let's check. The main issue is crashing on close, so yes, they seem to be the same. Wait, but let me make sure. Both have the same Blender version (5.1.0), both report crashes when closing. Even though bug 2 has more details about addons and crash window, the core issue is the same. So the answer should be Yes? Wait, no, wait. Wait bug 1's steps are "open blender 5.1.0, close with X". Bug 2 says "crashes most of the time when closing" but doesn't specify exact steps like bug 1. But the description is about crashing on close. So yes, they are duplicates. So the answer is Yes? Wait, no, wait. Wait the user said to focus on Description and Steps. Let's check:
Bug 1 Description: Blender crashes when closing program.
Bug 2 Description: Blender crashes most of the time when closing.
Steps for Bug 1: Open blender 5.1.0, close with X.
Steps for Bug 2: Blender crashes most of the time when closing (no exact steps but implies closing). So both are about crashing on close, same version. So yes, they are duplicates. So answer is Yes? Wait, but maybe not? Wait no, because both have the same core issue. So the answer is Yes. Wait, but let me check again. The user said "if you are unsure, then respond 'No'". But here, the key points match: crashing on close, same Blender version. So yes, they are duplicates. So the answer is Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 25.386300000000002,
"duplicate_report_number": "155870"
}
Report flagged as duplicate by LLM
Crash on exit
https://projects.blender.org/blender/blender/issues/155416
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU NVIDIA Corporation NVIDIA 572.16 Vulkan Backend
Blender Version
Broken: version: 5.1.0 Beta, branch: blender-v5.1-release, commit date: 2026-03-07 10:54, hash:
21cc928ee21eWorked: 5.0.1
Short description of error
Blender 5.1 crashes every time I quit it.
Exact steps for others to reproduce the error
Quite blender > Crash
Crash Report attached
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce.
Bug report 1: Title is "Blender crashes when closing", description says Blender crashes when closing. Steps: open 5.1.0, close with cross, crash.
Bug report 2: Title is "Crash on exit", description says Blender 5.1 crashes every time quit. Steps: Quit blender > Crash.
Both are about Blender crashing when exiting/closing. The steps are similar (closing the app leads to crash). Even though system info and exact versions have minor differences, the core issue—crashing on close/exit—is the same. So they're duplicates.
JSON Data
{
"llm_judgement": true,
"processing_time": 9.462253,
"duplicate_report_number": "155416"
}