Crash using operator panel with quick smoke #55048
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#55048
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
system-info.txt
Blender Version
Broken: 2.79.4
c84b8d4801
Worked: (optional)
Short description of error
Blender is crashing when using operator panel or F6 to change quick smoke from smoke to fire or smoke+fire
Exact steps for others to reproduce the error
blender.crash.txt
terminal_session.txt
Added subscriber: @Timaroberts
Added subscriber: @LukasZiechmann
It doesn't crash for me - but if I switch to smoke+fire the scene freezes for a fraction of a second and in the console the following is printed:
loadTile: No noise tile '/tmp/blender_oVxHhr/noise.wavelets' found.
Generating new 3d noise tile size=128^3
saveTile: Noise tile file '/tmp/blender_oVxHhr/noise.wavelets' saved.
Generating new 3d noise done
So I guess there goes something wrong while opening/saving this noise.wavelets file - maybe your system runs out of memory, but definitely something a developer should have a look at.
Added subscribers: @ideasman42, @lichtwerk
@LukasZiechmann: What you are seeing is actually nothing to worry about afaik. Did you test this in master? Or 2.79 official release?
Because in master there is indeed a real crash, relating to the UNDO refactor:
In
BKE_undosys_step_undo_with_data()
the UndoStep is still "Quick Smoke"but gets changed in
BKE_undosys_step_undo_with_data_ex()
to "Enter Editmode"Then in
mesh_undosys_step_decode()
the MeshUndoStepObject->obedit_ref.ptr is NULLWe have a couple of reports relating to the UNDO refactor (I should really familiarize with the system more), but for now assigning to @ideasman42
@LukasZiechmann: btw: I sometimes forget this myself, but note that it's always best to have someone to assign the report to when you triage as "confirmed" (otherwise chances are higher the report gets skipped in searches)
@lichtwerk : Sorry - Yes, I just tested it with the 2.79b-official release where it works fine. And I didn't know I was allowed to just assign confirmed bugs to someone - I guess always to the relevant module owner, right? Thanks for pointing all this out!
Changed status from 'Open' to: 'Resolved'
Fixed
9636cab009