Segmentation fault while texture painting #99015

New Issue

Péter Friedrich · 2022-06-20T15:04:05+02:00

Péter Friedrich commented

2022-06-20 15:04:05 +02:00

System Information
Operating system: Linux-5.15.0-37-lowlatency-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06

Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691
Worked: -

Short description of error
Attempting to texture paint on certain models results in segementation fault.

Exact steps for others to reproduce the error
Open the attached blend file, start painting on forearm_drone_kit.L (texture to paint on: DroneController, 2K)
os_info.txt

blender_3_2_0_segfault_while_painting.blend
blender_3_2_0_segfault_while_painting.crash.txt

**System Information** Operating system: Linux-5.15.0-37-lowlatency-x86_64-with-glibc2.35 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.129.06 **Blender Version** Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: `e05e1e3691` Worked: - **Short description of error** Attempting to texture paint on certain models results in segementation fault. **Exact steps for others to reproduce the error** Open the attached blend file, start painting on forearm_drone_kit.L (texture to paint on: DroneController, 2K) [os_info.txt](https://archive.blender.org/developer/F13207266/os_info.txt) [blender_3_2_0_segfault_while_painting.blend](https://archive.blender.org/developer/F13207267/blender_3_2_0_segfault_while_painting.blend) [blender_3_2_0_segfault_while_painting.crash.txt](https://archive.blender.org/developer/F13207268/blender_3_2_0_segfault_while_painting.crash.txt)

Péter Friedrich commented

2022-06-20 15:04:05 +02:00

Added subscriber: @peterf-2

Kévin Dietrich commented

2022-06-20 15:19:21 +02:00

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

Péter Friedrich commented

2022-06-20 15:36:29 +02:00

Forget to mention in the original post: painting in the 3D view causes the crash, painting in the 2D image view still works.

Philipp Oeser commented

2022-06-20 16:33:13 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-06-20 16:33:13 +02:00

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

Philipp Oeser commented

2022-06-20 16:33:13 +02:00

getting crashes in 3.1, 3.0.1, 2.93 as well

The mesh seems corrupt, the following returns True

C.active_object.data.validate_material_indices()

After that, painting succeeds.
@peterf-2 : got an idea how this thing got corrupted?

Thanks for the report. Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further.
Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.

getting crashes in 3.1, 3.0.1, 2.93 as well The mesh seems corrupt, the following returns True ``` C.active_object.data.validate_material_indices() ``` After that, painting succeeds. @peterf-2 : got an idea how this thing got corrupted? > Thanks for the report. Unfortunately unless there are clear instructions on how to reproduce it from scratch we cannot debug this any further. > Things that may cause mesh corruption: Importers, development versions of Blender, modeling tools.

Péter Friedrich commented

2022-06-20 17:54:56 +02:00

@lichtwerk: After C.active_object.data.validate_material_indices() it works on my side as well. Also can confirm that the error is present in older versions, while painting on the default cube works as expected.
No idea what went wrong, I did some fairly ugly booleans, though. If I read the help for validate_material_indices correctly, the issue was that individual polys got different material indices. What kind of operations could cause this? My workflow was this:

Basic polly modelling
Assign bevel weights to edges, add bevel modifier and weighted normals, enable autosmooth
Do booleans
Apply booleans, cleanup, adjust bevels
Assign material with UV grid
Unwrap, adjust
Assign new material with target texture (all textures are packed to the blend file)
Paint

Could any of these lead to this interesting error?
(I will continue working on the project to see if Ithe issue pops up again)
Thanks for the quick help!

@lichtwerk: After C.active_object.data.validate_material_indices() it works on my side as well. Also can confirm that the error is present in older versions, while painting on the default cube works as expected. No idea what went wrong, I did some fairly ugly booleans, though. If I read the help for validate_material_indices correctly, the issue was that individual polys got different material indices. What kind of operations could cause this? My workflow was this: 1) Basic polly modelling 2) Assign bevel weights to edges, add bevel modifier and weighted normals, enable autosmooth 3) Do booleans 4) Apply booleans, cleanup, adjust bevels 5) Assign material with UV grid 6) Unwrap, adjust 7) Assign new material with target texture (all textures are packed to the blend file) 8) Paint Could any of these lead to this interesting error? (I will continue working on the project to see if Ithe issue pops up again) Thanks for the quick help!

Philipp Oeser commented

2022-06-20 18:30:04 +02:00

I would suspect the booleans (of different objects with different materials) to somewhat leave invalid indices, not sure though.
Maybe you could run some tests if these lead to the buggy behavior?

I would suspect the booleans (of different objects with different materials) to somewhat leave invalid indices, not sure though. Maybe you could run some tests if these lead to the buggy behavior?

Péter Friedrich commented

2022-06-20 18:45:26 +02:00

Any particular tests in mind? Or shall I just go nuts with the booleans?

Kevin commented

2022-06-25 02:59:40 +02:00

Added subscriber: @jack.herbert

Kevin commented

2022-06-25 02:59:40 +02:00

I got that bug with a model made using boolean operations, also on Linux with an Nvidia card, and running the validate_material_indices line returns True and fixed it.

Philipp Oeser commented

2022-06-25 06:47:27 +02:00

Do you have an example file prior to applying the booleans that then crashes once the booleans are applied?

Kevin commented

2022-06-25 13:22:22 +02:00

Sadly no, I have a save from shortly after applying the modifier, don't know if that's any use but here it is:
texture-paint-crash.blend
Some observations:

When in edit mode, pressing Select in the material tab shows that a bunch of faces don't have any material assigned to them. They're in the "zone" of the boolean difference. Assigning them to the material also fixes the texture-paint crash.
I had a mirror modifier and it likely was in first position in the stack when I applied the boolean modifier.
The boolean cutting object (the cylinder) didn't have any material assigned to it.
When trying to do the same thing again (subtracting the cylinder from the main object), the new faces are correctly assigned to Material. So dunno how it happened the first time around.

Sadly no, I have a save from shortly after applying the modifier, don't know if that's any use but here it is: [texture-paint-crash.blend](https://archive.blender.org/developer/F13228945/texture-paint-crash.blend) Some observations: - When in edit mode, pressing Select in the material tab shows that a bunch of faces don't have any material assigned to them. They're in the "zone" of the boolean difference. Assigning them to the material also fixes the texture-paint crash. - I had a mirror modifier and it likely was in first position in the stack when I applied the boolean modifier. - The boolean cutting object (the cylinder) didn't have any material assigned to it. - When trying to do the same thing again (subtracting the cylinder from the main object), the new faces are correctly assigned to Material. So dunno how it happened the first time around.

Joseph Eagar commented

2022-06-27 01:20:47 +02:00

Added subscriber: @JosephEagar

Joseph Eagar commented

2022-06-27 01:20:47 +02:00

I can add a check in the paint code for invalid material slots. That said, we really should track down the booleans bug; I think I ran into it a few weeks ago.

Philipp Oeser commented

2022-08-08 09:29:32 +02:00

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

Philipp Oeser commented

2022-08-19 11:33:14 +02:00

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

Philipp Oeser commented

2022-08-19 11:33:14 +02:00

Since we do not have an example with the boolean modifier still active (not applied) and also since there have been related fixes (see a2d59b2dac & 1a6d0ec71c) I would assume the current situation has improved in 3.2.2 onwards (in that we hopefully dont run into this situation again).

That does not mean the original file is fixed, for that validate_material_indices is still necessary to fix the corruption.

I'll put this on hold for now, please use newer blender builds/versions and report back if you run into this situation again.

Since we do not have an example with the boolean modifier still active (not applied) and also since there have been related fixes (see a2d59b2dac & 1a6d0ec71c) I would assume the current situation has improved in 3.2.2 onwards (in that we hopefully dont run into this situation again). That does not mean the original file is fixed, for that `validate_material_indices` is still necessary to fix the corruption. I'll put this on hold for now, please use newer blender builds/versions and report back if you run into this situation again.

Philipp Oeser commented

2022-09-06 13:48:32 +02:00

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

Philipp Oeser closed this issue

2022-09-06 13:48:32 +02:00

Philipp Oeser commented

2022-09-06 13:48:32 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Philipp Oeser referenced this issue

2023-03-24 16:31:02 +01:00

.blend file crashing #106106

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

Segmentation fault while texture painting #99015