Crash after symmetrizing/duplicating bone (if an bActionGroup with that new name already exists) #118637

New Issue

Michael Colina · 2024-02-22T22:58:48+01:00

Michael Colina commented

2024-02-22 22:58:48 +01:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
blender crashes after symmetrizing an allegedly corrupted bone. this is not the first time and has happened randomly amongst several bones in different rigs i have been doing in b3d +4.0. and this problem had disappeared sometimes, but in the other hand when i couldn't find any way to fix it, then i discovered that by renaming the bone to a slightly or so different name for example: DEF-shoulder.L to DEF-shoulder1.L or DEF-shoulder.L.001 and then i was able to symmetrize again and kinda solved it, but it doesn't make any sense to do this workaround, so there is some obvious bone data corruption going on because then i tried to rename it back to the original name and symmetrize but then same bug and crash happens when the bone is specifically having the old name but not when having a new one... thanks devs for your help into looking this problem.

Exact steps for others to reproduce the error
Go to edit mode, select "CTRL-eye.L"
symmetrize that bone
then blender crashes

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** blender crashes after symmetrizing an allegedly corrupted bone. this is not the first time and has happened randomly amongst several bones in different rigs i have been doing in b3d +4.0. and this problem had disappeared sometimes, but in the other hand when i couldn't find any way to fix it, then i discovered that by renaming the bone to a slightly or so different name for example: DEF-shoulder.L to DEF-shoulder1.L or DEF-shoulder.L.001 and then i was able to symmetrize again and kinda solved it, but it doesn't make any sense to do this workaround, so there is some obvious bone data corruption going on because then i tried to rename it back to the original name and symmetrize but then same bug and crash happens when the bone is specifically having the old name but not when having a new one... thanks devs for your help into looking this problem. **Exact steps for others to reproduce the error** Go to edit mode, select "CTRL-eye.L" symmetrize that bone then blender crashes

Kangaroo-rig-bug.blend

8.9 MiB

Kangaroo-rig-bug.crash.txt

34 KiB

Michael Colina added the

labels 2024-02-22 22:58:49 +01:00

Philipp Oeser commented

2024-02-23 13:17:51 +01:00

Can confirm, will check

Philipp Oeser added

and removed

labels 2024-02-23 13:18:11 +01:00

Philipp Oeser referenced a pull request that will close this issue

2024-02-23 17:14:02 +01:00

Fix #118637: crash after editbone duplication in certain case #118676

Philipp Oeser commented

2024-02-23 17:15:16 +01:00

Fix is up, see !118676.

Will raise priority since this is a crasher

Fix is up, see !118676. Will raise priority since this is a crasher

❤️ 1

Philipp Oeser added

and removed

labels 2024-02-23 17:15:26 +01:00

Philipp Oeser changed title from ~~blender crashes after symmetrizing an allegedly corrupted bone~~ to Crash after symmetrizing/duplicating bone (if an bActionGroup with that new name already exists)

2024-02-23 17:32:17 +01:00

Philipp Oeser self-assigned this 2024-02-23 18:33:38 +01:00

Philipp Oeser referenced this issue from a commit

2024-02-26 17:41:05 +01:00

Fix #118637: crash after editbone duplication in certain case

Philipp Oeser closed this issue

2024-02-26 17:41:08 +01:00

Blender Bot added

Status

Resolved

and removed

Status