Crash on Exiting Texture Paint With Multiresolution (Image Editor involved) #81775
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
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
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#81775
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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 64 bit
Graphics card: Nvidia GTX 750 Ti
Blender Version
Broken: 2.90.1 release, 2.91 alpha
ba8233174c
Worked: 2.83.7
Introduced by: {1ceb91d1b3947fda67a70a2eff785a964e625ca2}
Short description of error
Switching from Texture Paint mode to Object Mode with an object that has a Multiresolution modifier, after sampling and then painting, crashes every time.
This makes Texture Painting with Multires impossible to use.
Exact steps for others to reproduce the error
texturepaint_exit.blend
Added subscriber: @Foaly
#80560 was marked as duplicate of this issue
#82298 was marked as duplicate of this issue
#81605 was marked as duplicate of this issue
Added subscriber: @EAW
Changed status from 'Needs Triage' to: 'Confirmed'
Thank you for the report. I can confirm that it crashes using 2.91
77aef03d8a
.It crashes 2.90.1 when starting Blender normally, or when using
blender_factory_startup.cmd
. 2.90.1 doesn't crash when usingblender_debug_log.cmd
orblender_debug_gpu.cmd
2.83.7 doesn't crash.
2.91 MSVC debug build stack trace:
{F9010015}
{F9010016}
{F9010063}
Slightly different stack trace when running
blender_debug_log.cmd
on a Release build:Note that the crash doesn't seem to happen if there is not Image Editor open.
And should this perhaps be High priority, considering this is a crash bug? (See https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook#Valid_crash_report.2C_can_confirm)
Added subscriber: @lichtwerk
I am seeing this as well (not reliably though, still trying to figure out how exactly this can be triggered 100% reproducable)
Also I dont get in a Debug build at all?
For Release builds, this seems to have started between good
baf124c753
and badf45f8a7a89
.So no luck nailing this to a particular commit that caused it, but I also think this deserves High priority.
Crash on Exiting Texture Paint With Multiresolutionto Crash on Exiting Texture Paint With Multiresolution (Image Editor involved)Added subscriber: @Jeroen-Bakker
@Jeroen-Bakker: does this ring a bell?
Added subscribers: @Diogo_Valadares, @iss, @mano-wii
I agree that it should have been set to high, I wanted to see if I could narrow down the cause further first. I got caught going down the rabbit hole of the fact that many seemingly unrelated crash reports stack traces all start with the same TBB code (that partially(?) has since been removed from their code base. (Difficult to figure out what is going on there as TBB's commit logs leave much to be desired in the documentation and size department.))
I did try retest this yesterday using 2.91
efc2edc47f
and noticed that it no longer crashes when changing to object mode. However, the sphere now disappears when I click to paint on it.Running
blender_debug_gpu.cmd
results in 227 occurrences of:GPUDebug: [2mTexture state usage warning: Texture 0 is base level inconsistent. Check texture size.[0m
and 8 occurrences of:
GPUDebug: [2mRasterization usage warning: Blending is enabled, but is not supported for integer framebuffers.[0m
blender_debug_output.txt
blender_system_info.txt
I'd also like to note that the root of the issue seems to be happening at the sampling (pressing S).
You can see that in the image editor the lines from wireframe disappear and it looks like it's drawn with "optimal display".
I will have a look as my name is all over it :-) Not sure what is actually going on. But will investigate starting with the drawing part.
I am not able to crash. It could be that the crash has already been solved. Still left are the glitches.
In Blender 2.83 the uv geometry in the uv editor also changes, will add that as a separate issue. I will keep this issue for the disapearing object.
I can confirm that this no longer crashes, but the object disappears instead.
yes, as evan said
The disappearing object is introduced by {1ceb91d1b3947fda67a70a2eff785a964e625ca2}
It seems like
draw_cache_impl_mesh
perfors a save clearbut the
MBC_SURFACE
batch isn't picked up bymesh_buffer_cache_create_requested
.Added subscriber: @Manndarinchik
This issue was referenced by
7a7f294940
Changed status from 'Confirmed' to: 'Resolved'
Added subscribers: @Ekiwnox, @rjg, @brecht, @coindrop, @ankitm