Instanced Arrayed Object Crashing Blender #125
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/test#125
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/157212
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 595.71 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: (unsure as dont know how to go back to previous versions)
Short description of error
[I am making a tank track, and have a plane as the parent to my tank tread, I apply an Array modifier to the plane, then a deform curve modifier, selecting my curve which exists as the one to follow, and then when I hit Tab to switch out of edit mode, blender crashes. Note that i have instancing faces enabled.]
Exact steps for others to reproduce the error
[I've assembled a quick "scene" so you're able to recreate the issue. All you should need to do is left click on the arrayed object, and then hit tab. It should then crash. I've repeated this exact process both on my actual project. as well as this recreation of the issue, and it consistently crashes on both. Thank you for your time and I look forward to hearing back from you. Cheers]
[Based on the default startup or an attached .blend file (as simple as possible)]
Report is clear
LLM Reasoning
Got it, let's see. The bug report has a title, system info (but we ignore that), blender version, short description of error, and exact steps to reproduce. The steps are clear: left click arrayed object, hit tab, crash. The description explains the setup with plane parent, array modifier, deform curve, instancing faces enabled. So the clarity is good. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 6.239956
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title is "Instanced Arrayed Object Crashing Blender". The body describes a specific scenario: making a tank track with a plane parent, applying Array modifier, then deform curve, and crashing when switching out of edit mode. The exact steps are given to reproduce the error. So it's about a specific issue because it details a particular workflow (tank track creation) that leads to the crash. The user provides exact steps, which makes it specific. So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 7.723242
}
Report flagged as duplicate by LLM
Hard crash when going into edit mode on an object after using "Make Instance Face" and then dublicating the object.
https://projects.blender.org/blender/blender/issues/156158
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 572.16 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
Hard crash when going into edit mode on an object after using "Make Instance Face" and then dublicating the object.
Exact steps for others to reproduce the error
Steps from scratch
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug Report 1: The issue is when using an Array modifier with instancing faces enabled on a plane (tank tread), then switching to edit mode causes a crash. Steps involve arraying the object, applying deform curve, then tab to edit mode.
Bug Report 2: The issue is after using "Make Instance Face" and duplicating the object, going into edit mode crashes. Steps are adding a plane, making instance face, duplicating, then entering edit mode.
Wait, let's check the key elements. Both involve instancing faces (Report 1 has "instancing faces enabled", Report 2 uses "Make Instance Face"). Then both have crashing when entering edit mode. But Report 1 mentions Array modifier and deform curve, while Report 2 is about duplicating after Make Instance Face. Are these the same underlying issue?
Wait, maybe the core is instancing faces leading to crash on edit mode. Let's see: Report 1's steps include array (which might use instance face), then deform curve, then tab. Report 2's steps are make instance face, duplicate, then edit mode. The common factor is instancing faces and crashing when entering edit mode. But do the steps align? Report 1 has array + deform curve, Report 2 has make instance face + duplicate. Are these different workflows but same bug?
Wait, maybe the "Make Instance Face" in Report 2 is similar to what's happening in Report 1 (since Array modifier with instancing faces enabled would use that). So both involve instanced faces and crash on edit mode. But let's check if the steps are equivalent. Report 1: array (with instance face) + deform curve, then tab. Report 2: make instance face + duplicate, then edit. Are these two different scenarios but same bug? Or different?
Wait, the question is whether they are the same issue. Let's see the descriptions:
Report 1: Crashing when switching to edit mode after array (with instancing faces) and deform curve.
Report 2: Crashing when entering edit mode after make instance face and duplicating.
The common element is instancing faces leading to crash on edit mode. But are the steps causing the same bug? Maybe, but let's check if the triggers are similar. Report 1 has array + deform curve, Report 2 has make instance face + duplicate. Are these two different ways to trigger the same underlying issue with instanced faces and edit mode?
Alternatively, maybe they are different. But the user says to focus on Description and Steps. Let's see:
Report 1 steps: Left click arrayed object, hit tab → crash.
Report 2 steps: After make instance face + duplicate, go into edit mode → crash.
The core is instanced faces and crash on edit mode. So maybe they are the same issue. But wait, Report 1 has Array modifier (which uses instance face) and deform curve, while Report 2 has Make Instance Face directly. Are these two different workflows but same bug?
Alternatively, maybe not. Let's think: if the bug is in instanced faces handling when entering edit mode, then both reports are about that. So maybe "Yes". But wait, let's check the exact steps. Report 1's steps involve array (which may create instances) and deform curve, then tab. Report 2's steps are make instance face + duplicate, then edit. Are these two different scenarios but same bug?
Alternatively, maybe they are duplicates because both involve instanced faces leading to crash on edit mode. So the answer would be "Yes". Wait, but let's confirm.
Wait, the user says: focus primarily on Description and Steps. Let's recheck:
Report 1 Description: Crashing when switching to edit mode after array (with instancing faces) and deform curve.
Report 2 Description: Hard crash when going into edit mode after make instance face and duplicating.
Steps for Report 1: Click arrayed object, hit tab → crash.
Steps for Report 2: After make instance face + duplicate, go into edit mode → crash.
The common factor is instanced faces (either via array or make instance face) leading to crash on edit mode. So maybe they are the same issue. Therefore, answer is "Yes".
JSON Data
{
"llm_judgement": true,
"processing_time": 47.959300000000006,
"duplicate_report_number": "156158"
}
Report flagged as NOT a duplicate by LLM
After creating an instanced face and entering Edit Mode, the software crashes.
https://projects.blender.org/blender/blender/issues/149206
System Information
Operating system: Windows 11 Professional
Graphics card: NVIDIA GeForce RTX 4080 Ti
Blender Version
Broken version: Blender 5.1.0 Alpha (main branch, commit hash 4d274768c649 , compiled on 2025-10-31)
Worked: 5.0
Exact steps to reproduce the issue
Object -> Relationships -> Make Instance Facefrom the top of the 3D viewportLLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps.
Bug report 1: The issue is when using an Instanced Array (with instancing faces enabled) on a plane, applying deform curve, then switching to edit mode (Tab) causes crash. Steps involve selecting arrayed object and hitting Tab.
Bug report 2: Steps are creating instance face on a cube, moving it away, entering edit mode, which crashes. The key here is "instanced face" and entering edit mode causing crash.
Wait, the first one uses Array modifier with instancing faces, then deform curve, then Tab (edit mode). The second is Make Instance Face, then enter edit mode. Are these the same underlying issue? Let's check the core actions: both involve instanced objects (arrayed or instance face) and entering edit mode causing crash. But the first has an array modifier plus deform curve, the second is just make instance face. However, the common element is "instanced" object + entering edit mode leading to crash. But are they the same issue? Let's see the steps:
Report 1: Array modifier (with instancing faces) → deform curve → Tab (edit mode) → crash.
Report 2: Make Instance Face → enter edit mode → crash.
The first involves an array modifier, the second is a direct instance face. But maybe the underlying issue is related to instanced objects in edit mode. However, the steps are different. Wait, but the question is if they are the same issue. Let's check the descriptions. Report 1 mentions "instancing faces enabled" (from Array modifier), report 2 is "Make Instance Face". So both involve instance faces. The crash happens when entering edit mode in both cases. But the first has additional modifiers (Array, deform curve) while the second doesn't. Are these duplicates? Maybe not, because the steps are different. Wait, but maybe the core issue is instanced objects in edit mode causing crash, regardless of other modifiers. But let's see: Report 1's steps are selecting arrayed object and hitting Tab (edit mode). Report 2's steps are make instance face, then enter edit mode. So both involve entering edit mode on an instanced object. But the first has an array modifier, the second is a direct instance. Are these considered the same issue? The question says to focus on Description and Steps. Let's compare:
Report 1 description: "I apply an Array modifier to the plane, then a deform curve modifier... when I hit Tab to switch out of edit mode, blender crashes. Note that i have instancing faces enabled."
Report 2 steps: "Make Instance Face" → enter edit mode → crash.
So both involve instanced objects (array with instancing faces vs make instance face) and entering edit mode causing crash. But the first has additional modifiers. However, maybe the underlying bug is about instanced objects in edit mode. But are they duplicates? Let's think: if two reports have different steps but same core issue (instanced object + edit mode crash), maybe yes. But wait, report 1's crash happens when exiting edit mode (Tab from edit to object mode?), while report 2 is entering edit mode. Wait, no: Report 1 says "when I hit Tab to switch out of edit mode" – so going from edit to object mode. Report 2 says "entering edit mode". So different actions (exit vs enter). Hmm. That's a difference. Also, the first has array + deform curve, the second is just make instance face. So maybe they are not the same. Wait, but let's check again. The key is whether the steps and descriptions point to the same issue. Report 1: array modifier with instancing faces, deform curve, then Tab (exit edit mode) → crash. Report 2: make instance face, enter edit mode → crash. Different actions (enter vs exit), different modifiers. So probably not duplicates. Therefore, answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 44.326028,
"duplicate_report_number": "149206"
}
Report flagged as duplicate by LLM
Crash when entering object editing mode with an instancing object
https://projects.blender.org/blender/blender/issues/155986
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060 6GB NVIDIA Corporation NVIDIA 576.52 Vulkan Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: 5.0
Caused by a958e3d6b7c5b1a7ad20c1b276c9e404f79c0650
Short description of error
Entering object editing mode with an instancing object. Instancing is done through the object-instancing menu of the face type.
The crash occurs immediately after changing the mode.
Exact steps for others to reproduce the error
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps.
Bug report 1: The user is using an Array modifier with instancing faces on a plane (parent to tank tread), then switching to edit mode (Tab) causes crash. Steps involve clicking arrayed object and hitting Tab.
Bug report 2: Entering object editing mode (edit mode) with an instancing object (face type). Steps are create two objects, parent them, enable face instancing in parent, enter edit mode.
Wait, the key here is the action that causes crash. Both involve entering edit mode (Tab) when there's an instanced array or face instancing. But let's check the details. Report 1 uses Array modifier with instancing faces, report 2 uses object-instancing menu for face type. Are these the same underlying issue? The steps are similar: both involve entering edit mode on an object with some form of instancing (array vs face instancing). But maybe the specific modifiers differ. However, the core action is entering edit mode causing crash when instancing is involved.
Wait, but let's check the exact steps. Report 1: array modifier + deform curve, then Tab. Report 2: object-instancing face menu, then enter edit mode. Are these two different scenarios or same? The question is if they are duplicates. Let's see the description: both involve crash when entering edit mode with instancing. But maybe the specific setup (array vs object-instancing) is different. However, the user might be reporting the same underlying bug where entering edit mode on an instanced object crashes Blender, regardless of how the instancing is set up.
But wait, let's check the steps again. Report 1: arrayed object (with instancing faces) → Tab. Report 2: parent with face instancing → enter edit mode. So both are about entering edit mode on an object that has some form of instancing, leading to crash. Are these considered the same issue? Maybe, but let's see if the steps are similar enough.
Alternatively, maybe they are different because one uses Array modifier and the other uses object-instancing menu. But the core action is entering edit mode causing crash with instancing. However, the problem might be in how Blender handles instanced objects when switching to edit mode. So perhaps they are duplicates. But wait, let's check the exact steps. Report 1: after applying Array and deform curve, Tab. Report 2: after enabling face instancing, enter edit mode. Are these two different scenarios or same?
Wait, the user is asking if based on description and steps, they are the same. Let's see:
Report 1: Instanced Arrayed Object (Array modifier) → crash when switching to edit mode.
Report 2: Crash when entering object editing mode with an instancing object (face type via object-instancing menu).
So both involve entering edit mode on an object that has instancing, leading to crash. The difference is the method of instancing (Array modifier vs object-instancing menu). But maybe the underlying bug is the same: Blender crashes when entering edit mode on any instanced object, regardless of how it's set up.
But let's check if the steps are similar enough. Report 1's steps: click arrayed object → Tab. Report 2's steps: create parent with face instancing → enter edit mode. So both involve entering edit mode on an instanced object. So maybe they are duplicates.
Alternatively, maybe not. Let's think again. The first report uses Array modifier (which is a specific modifier), the second uses object-instancing menu (a different way to instance). But the crash occurs when entering edit mode in both cases. So perhaps they are the same issue. But I need to decide if they are duplicates.
Wait, the question says "based on the text description of these two bug reports, are they the same issue?" focusing on Description and Steps.
Report 1's description: making tank track with plane parent, array modifier, deform curve, instancing faces enabled → crash when Tab (switch to edit mode).
Report 2's description: entering object editing mode with instancing object (face type) → crash immediately after changing mode.
Steps for report 1: click arrayed object → Tab.
Steps for report 2: create two objects, parent, enable face instancing in parent, enter edit mode.
So both involve entering edit mode on an object that has some form of instancing, leading to crash. The difference is the method of instancing (Array vs object-instancing). But maybe the underlying bug is the same: Blender crashes when entering edit mode on any instanced object. So perhaps they are duplicates.
But wait, maybe the first report's issue is specific to Array modifier with deform curve, while the second is about face instancing via object menu. But the user might be reporting two different instances of the same bug. Alternatively, maybe not.
Alternatively, let's check if the steps are similar enough. Report 1: after setting up array and deform, Tab. Report 2: after enabling face instancing, enter edit mode. So both involve entering edit mode on an instanced object. So yes, they could be duplicates.
But I need to make a decision. Let's see: the core action is entering edit mode causing crash with instancing. So maybe "Yes". But wait, maybe not. Let me think again.
Wait, report 1 uses Array modifier (which is a specific modifier), report 2 uses object-instancing menu. Are these two different ways to instance? Yes. But the crash occurs when entering edit mode in both cases. So perhaps they are duplicates because the root cause is the same: handling instanced objects during edit mode transition.
Alternatively, maybe not. Let's see the exact steps. Report 1: arrayed object (with instancing faces) → Tab. Report 2: parent with face instancing → enter edit mode. So both involve entering edit mode on an instanced object. So yes, they are duplicates.
But I'm not 100% sure. However, the question says if unsure, respond "No". But maybe they are duplicates. Wait, let's check the titles: "Instanced Arrayed Object Crashing Blender" vs "Crash when entering object editing mode with an instancing object". The first is about arrayed object, second about any instancing object. So maybe the second is a more general case of the first. So they could be duplicates.
Alternatively, maybe not. Let's see: report 1 has Array modifier and deform curve, report 2 has object-instancing menu. But the crash occurs when entering edit mode in both. So perhaps yes.
But I think the answer is "Yes" because both involve crashing when entering edit mode on an instanced object, regardless of how it's set up.
JSON Data
{
"llm_judgement": true,
"processing_time": 74.07022,
"duplicate_report_number": "155986"
}
Report flagged as NOT a duplicate by LLM
Crash when entering edit mode on an instantiated mesh
https://projects.blender.org/blender/blender/issues/156695
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5090 NVIDIA Corporation NVIDIA 595.79 Vulkan Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3Worked: unconfirm
Short description of error
Crash every time when entering edit mode on an instantiated mesh
Exact steps for others to reproduce the error
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the description and steps to reproduce.
Bug Report 1: The issue is when using an Instanced Array (with faces enabled) on a plane parented to a tank tread, applying array and deform curve modifiers, then switching out of edit mode (Tab) causes crash. Steps involve clicking the arrayed object and hitting Tab.
Bug Report 2: Crash when entering edit mode on an instantiated mesh. Steps are adding a plane, selecting cube and plane, parenting with face instancing, then entering edit mode on parent.
Wait, let's check the key points. Both involve instanced meshes (array or faces instancing) and crashes related to edit mode (entering or exiting). But the steps differ: Report 1 is about exiting edit mode (Tab), Report 2 is entering edit mode. Also, Report 1 has array + deform curve modifiers, Report 2 is just parent with face instancing. Are these the same underlying issue? Let's see the core problem: both involve instanced meshes and crashes during edit mode transitions. But the steps are different—one is exiting, one is entering. However, maybe the root cause is similar (instanced mesh + edit mode). Wait, but let's check the descriptions again.
Report 1: "when I hit Tab to switch out of edit mode, blender crashes" with instanced array and deform curve. Report 2: "Crash every time when entering edit mode on an instantiated mesh". So one is exiting, one is entering. But maybe they are related but not the same. Wait, but let's check if the steps could be similar. Report 1's steps: left click arrayed object, hit Tab (exit). Report 2: enter edit mode on parent with face instancing. Are these the same issue? Let's see the system info: both have Windows 11, RTX cards, Blender 5.1.0. But the error descriptions are different—one is exiting, one is entering. So maybe not the same. Wait, but maybe the underlying bug is about instanced meshes and edit mode transitions. However, the steps to reproduce are different (exit vs enter). So I think they are not the same issue. Therefore, answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 27.246232,
"duplicate_report_number": "156695"
}
Report flagged as NOT a duplicate by LLM
Blender 5.0 Reproducible crash when deleting object with the new Array modifier
https://projects.blender.org/blender/blender/issues/147261
System Information
Operating system: Windows 11 Pro
Graphics card: Nvidia RTX 3060
Blender Version
Broken: Blender 5.0 Alpha, cc687df8eae9
Worked: broken ever since introduced
Short description of error
Crash when deleting an object with the new Array modifier
Exact steps for others to reproduce the error
Based on the attached .blend file:
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps for each.
Bug Report 1: The issue is when using an Instanced Array (with faces enabled) on a plane with a deform curve modifier, then switching to object mode (Tab) causes a crash. Steps involve selecting the arrayed object and hitting Tab.
Bug Report 2: The issue is deleting an object that has a circular array modifier applied, which causes a crash. Steps are select the cube with array modifier, try to delete it, crash.
The key here is the actions causing the crash: one is switching to object mode (Tab) after using array and deform modifiers, the other is deleting an object with array modifier. These are different actions (mode switch vs deletion) and different contexts (instanced array with deform curve vs circular array). So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.128884999999999,
"duplicate_report_number": "147261"
}