Mouse movement causes crash during particle bake #80752

Open
opened 2020-09-13 18:19:56 +02:00 by Thomas Mann · 8 comments

System Information
Operating system: Win10
Graphics card: GTX2060

Blender Version
Broken: 2.90, 0330d1af29, master, 2020-08-31

Short description of error
Reproducible crash when baking particle animation and moving mouse

Short description of error
Sadly, I was not able to reproduce the crash in a simpler file, so I assume it has to be related to the current boid setup with lots of drivers.

Exact steps for others to reproduce the error

  1. Load the attached blend file
  2. Make sure Workspace is set to layout
  3. Select one of the two particle-emitters
  4. Click bake
  5. During bake move the mouse over Render or Graph views
  • Crash

Also see this video capture: https://youtu.be/VIUy6r9S-Hk (It ends in the moment of the crash)

swarm-test1.crash.txt

swarm-test2-crash.blend

**System Information** Operating system: Win10 Graphics card: GTX2060 **Blender Version** Broken: 2.90, 0330d1af29c0, master, 2020-08-31 **Short description of error** Reproducible crash when baking particle animation and moving mouse **Short description of error** Sadly, I was not able to reproduce the crash in a simpler file, so I assume it has to be related to the current boid setup with lots of drivers. **Exact steps for others to reproduce the error** 1. Load the attached blend file 2. Make sure Workspace is set to layout 3. Select one of the two particle-emitters 4. Click bake 5. During bake move the mouse over Render or Graph views - > Crash Also see this video capture: https://youtu.be/VIUy6r9S-Hk (It ends in the moment of the crash) [swarm-test1.crash.txt](https://archive.blender.org/developer/F8873100/swarm-test1.crash.txt) [swarm-test2-crash.blend](https://archive.blender.org/developer/F8873153/swarm-test2-crash.blend)
Author

Added subscriber: @pixtur

Added subscriber: @pixtur

Added subscriber: @mano-wii

Added subscriber: @mano-wii

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

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

Thanks for the report, I can confirm the issue with either the latest stable or current development versions of Blender:

>	blender.exe!ptcache_particle_read(int index, void * psys_v, void * * data, float cfra, const float * old_data) Line 336	C

 	blender.exe!ptcache_read(PTCacheID * pid, int cfra) Line 2999	C
 	blender.exe!BKE_ptcache_read(PTCacheID * pid, float cfra, bool no_extrapolate_old) Line 3134	C
 	blender.exe!system_step(ParticleSimulationData * sim, float cfra, const bool use_render_params) Line 4517	C
 	blender.exe!particle_system_update(Depsgraph * depsgraph, Scene * scene, Object * ob, ParticleSystem * psys, const bool use_render_params) Line 4936	C
 	blender.exe!BKE_object_handle_data_update(Depsgraph * depsgraph, Scene * scene, Object * ob) Line 257	C
 	blender.exe!BKE_object_eval_uber_data(Depsgraph * depsgraph, Scene * scene, Object * ob) Line 385	C
 	[External Code]	
 	blender.exe!blender::deg::`anonymous namespace'::deg_task_run_func(TaskPool * pool, void * taskdata) Line 128	C++
 	[External Code]	
 	blender.exe!tbb::interface7::internal::isolate_impl<void,void <lambda>(void) const>(const Task::()::__l2::void <lambda>(void) & f) Line 160	C++
 	blender.exe!Task::operator()() Line 122	C++
 	blender.exe!tbb::internal::function_task<Task>::execute() Line 1049	C++
 	[External Code]	
Thanks for the report, I can confirm the issue with either the latest stable or current development versions of Blender: ```lines > blender.exe!ptcache_particle_read(int index, void * psys_v, void * * data, float cfra, const float * old_data) Line 336 C blender.exe!ptcache_read(PTCacheID * pid, int cfra) Line 2999 C blender.exe!BKE_ptcache_read(PTCacheID * pid, float cfra, bool no_extrapolate_old) Line 3134 C blender.exe!system_step(ParticleSimulationData * sim, float cfra, const bool use_render_params) Line 4517 C blender.exe!particle_system_update(Depsgraph * depsgraph, Scene * scene, Object * ob, ParticleSystem * psys, const bool use_render_params) Line 4936 C blender.exe!BKE_object_handle_data_update(Depsgraph * depsgraph, Scene * scene, Object * ob) Line 257 C blender.exe!BKE_object_eval_uber_data(Depsgraph * depsgraph, Scene * scene, Object * ob) Line 385 C [External Code] blender.exe!blender::deg::`anonymous namespace'::deg_task_run_func(TaskPool * pool, void * taskdata) Line 128 C++ [External Code] blender.exe!tbb::interface7::internal::isolate_impl<void,void <lambda>(void) const>(const Task::()::__l2::void <lambda>(void) & f) Line 160 C++ blender.exe!Task::operator()() Line 122 C++ blender.exe!tbb::internal::function_task<Task>::execute() Line 1049 C++ [External Code] ```

Added subscriber: @Nubnubbud

Added subscriber: @Nubnubbud

I have more information on this event. it's not linked to individual settings, and with various files, I can trigger it I was also unable to reproduce after simplifying my files totally, but adding forces, using the emitter as a flow object (and one set to use particles) seems to make it far easier to come by (happens more immediately when attempting to cause crash).
however, I have a test case where this happens regardless of the bake used, so long as it's a physics bake at all.
This is still an issue up to blender 3.0, I tested with the new cycles x alpha.

I have also confirmed that this file has the same issue on Windows and a Mac

I was working with a client when we came across it, and it completely halted production, as it completely rendered the file (a finished scene based on particle and dust sims) inoperable.
I have also noticed that particle sims behave strangely (speed up and slow down on rather speedy sims) when the mouse is moving around the workspace, and crossing the borders between editors. There's definitely something in there making its performance unstable, perhaps a rare event, that becomes more likely when all these factors are in play.

Here's the file. it has both a particle bake and a volume sim bake. Both cause the same issue. The force is not needed, but appears to make the crash far more likely by adding stressors to the simulations.
how to crash

  • select either the domain(smoke), or cylinder(particle)
  • start bake
  • wave cursor around, targeting mainly the 3D viewport, properties editor, and where the two touch.
  • enjoy the crash

Dustsimplified2.blend

I have more information on this event. it's not linked to individual settings, and with various files, I can trigger it I was also unable to reproduce after simplifying my files totally, but adding forces, using the emitter as a flow object (and one set to use particles) seems to make it far easier to come by (happens more immediately when attempting to cause crash). **however, I have a test case where this happens regardless of the bake used, so long as it's a physics bake at all.** This is still an issue up to blender 3.0, I tested with the new cycles x alpha. **I have also confirmed that this file has the same issue on Windows and a Mac** I was working with a client when we came across it, and it completely halted production, as it completely rendered the file (a finished scene based on particle and dust sims) inoperable. I have also noticed that particle sims behave strangely (speed up and slow down on rather speedy sims) when the mouse is moving around the workspace, and crossing the borders between editors. There's definitely something in there making its performance unstable, perhaps a rare event, that becomes more likely when all these factors are in play. Here's the file. it has both a particle bake and a volume sim bake. Both cause the same issue. The force is not needed, but appears to make the crash far more likely by adding stressors to the simulations. **how to crash** - select either the domain(smoke), or cylinder(particle) - start bake - wave cursor around, targeting mainly the 3D viewport, properties editor, and where the two touch. - enjoy the crash [Dustsimplified2.blend](https://archive.blender.org/developer/F10569757/Dustsimplified2.blend)

Added subscriber: @Francesco-Della-Torre

Added subscriber: @Francesco-Della-Torre

This comment was removed by @Francesco-Della-Torre

*This comment was removed by @Francesco-Della-Torre*
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:46:32 +01:00
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#80752
No description provided.