Blender 2.80 - Removing second Particle System cache causes crash #59958
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#59958
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
Graphics card: GTX 1070
Blender Version
Broken: 2.80,
7c438e5366
, 2018-12-28 23:19, as found on the splash screen (from buildbot)Short description of error
Changing particle system settings after removing second particle system cache causes crash
Exact steps to reproduce the error
EXCEPTION_ACCESS_VIOLATION
.Alternative steps
Saving file before adding the second cache doesn't affect the crash.
Added subscriber: @ixd
Added subscriber: @ZedDB
I can't seem to reproduce this on my end. Is this still a problem with the latest blender beta?
@ZedDB Yep. It still crashes for me. Also tested on a different machine running Ubuntu 18.10 x64 - it crashes. More info:
Win 10 (
1d908bffdd
)When running
blender.exe --debug-all
it crashes more rarily (like in 1 of 3 test runs) but here some useful console output (when blender doesn't crash immediately):Right after 7. Change Particles tab -> Emission -> Frame Start to any value:
and after closing blender:
Ubuntu 18.10 (
7f77961f1c
)It doesn't crash after the aforementioned steps, but it does when running with
--debug-memory
switch.Output from
blender --debug-memory
:Content of
blender.crash.txt
:Output from
blender --debug-all
:Also clicking on the freshly added cache item increases reported memory consumption:
How to reproduce (click to view gif):
I can reproduce this on
7f77961f1c
.However, I couldn't yesterday and not today either with the latest commit. So I'm guessing this was fixed sometime yesterday (and my build that I tested with was new enough to have this fix in).
Could you see if you can reproduce this again (on both linux and windows) with the current builds from the build bot?
Wait, now I'm getting this still on the latest commit :S
Why couldn't I trigger this before I rolled back to the commit you listed...
Ugh, anyways. I can reproduce this on my side with the latest commit.
Added subscriber: @mont29
Feel free to reassign if this is not for you @mont29
Just missing a DEG tagging, fix incoming.
This issue was referenced by
ea5326df86
Changed status from 'Open' to: 'Resolved'