Regression: Blender crashes when texture painting (caused by boolean modifers) #99191
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#99191
Loading…
Reference in New Issue
Block a user
No description provided.
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?
System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40
Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash:
e05e1e3691
Worked: 3.1.2
Caused by
1a6d0ec71c
.Short description of error
Blender crashes when texture painting a model.
Reason is boolean modifiers will leaving "invalid"
mat_nr
around.Exact steps for others to reproduce the error
T99191_repro.blend
Original report Exact steps for others to reproduce the error
I created a simple material to render peeling paint on a metal surface, I try to paint a black and white image to generate the normal bump. But Blender crashes after the third clicks.
Here my blend file :
terminals2.blend
and here my crash file :
terminals2.crash.txt
My graphic card's drivers are updated and I also tried Blender 2.92, but the crash still occurs.
Added subscriber: @smol
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi, thanks for the report.
I've not been able to repro crash in 3.3 (but I can in 3.2)
@smol, could you check in 3.2.1 or 3.3: https://builder.blender.org/download/daily/ (I'll also check in 3.2.1)
Changed status from 'Needs User Info' to: 'Confirmed'
Can replicate crash in 3.2.1 too. Bisecting (I mean finding the commit for backporting).
I did some cleanup in your file and I can now repro crash even in 2.93-3.3
lowering the priority.
@PratikPB2123 Thank you for your time. I also tried in 3.2.1 but it still crashes. Do you have any idea on how can I avoid this crash until the problem is fixed ?
Added subscribers: @howardt, @lichtwerk
Ha! I think we finally found a case where the boolean modifier screws with material indices?
Disabling all boolean modifiers lets you paint on the thing, enabling one and trying to paint makes it go Boom!
Then, there is BMFace with mat_nr -1 which crashes here for me
CC @howardt
Blender crashes when texture paintingto Blender crashes when texture painting (caused by boolean modifers)@PratikPB2123 : do you have the cleaned up file that also crashes in 2.93? (cannot repro)
terminals2-cleanup.blend
This file and the one attached in the report gives identical call stack to me
Added subscriber: @HooglyBoogly
@PratikPB2123 : have you done the cleanup [applying the booleans] in 3.2 (or a later build)?
If you do the same cleanup in 2.93, does it also crash?
In your backtracke, the root problem is the same : a borked
mat_nr
(this time onMPoly
)To me, this is caused by
1a6d0ec71c
.From that commit on, the original file asserts on open (see my stacktrace)
Applying boolean modifiers will leave those "invalid"
mat_nr
around.Also found a simpler repro case:
T99191_repro.blend
And will raise prio since this looks like a regression to me.
CC @HooglyBoogly
Blender crashes when texture painting (caused by boolean modifers)to Regression: Blender crashes when texture painting (caused by boolean modifers)Not quite sure why those
material_remaps
Arrays always have a minimum size of 1?Even if both participating objects dont have materials at all (nothing gets done with that array then)?
Could it be uninitialized memory (I do see all sorts of other indices in mat_nr, not only -1 ...)
Hmm, I think the invalid part might be that the
material_remaps
are created on the object level. Maybe it works in some cases, but I think including object-linked materials in these remaps is problematic and more trouble than its worth.To me, object-level materials seem more like a post-evaluation step that shouldn't be considered when retrieving data from other objects.
I guess it depends how much behavior change we can accept, but to me the best/simplest solution is using the same code for remapping as the node.
No crash if I do so.
#99371, #99349, #99174 seem to be other incarnations of this
#99322, #98705 also.
This issue was referenced by
a2d59b2dac
Changed status from 'Confirmed' to: 'Resolved'
Changed status from 'Resolved' to: 'Confirmed'
I'll reopen this until the patch is committed to master as well.
This issue was referenced by
5723bf926d
Changed status from 'Confirmed' to: 'Resolved'