Page MenuHome

F12 and crash
Closed, ResolvedPublicBUG

Description

Windows 10 64, gtx 970

Blender 2.79

Just open the file and press f12 and crash

Event Timeline

in cycles using gpu render

Ray Molenkamp (LazyDodo) lowered the priority of this task from 90 to 50.Sep 16 2017, 6:06 PM

It's a null ref in particles.c ( psys_thread_create_path ) @Bastien Montagne (mont29) mind taking a peek here?

Bah… yet another mismatch between rendering data and regular scene update data, here there are less child particles for rendering (5) than for 3DView (30), so when rendering data update process (re-)allocates memory for 5 children, but then regular scene update, which happens in parallel, tries to use that allocated cache for 30 children, it obviously breaks…

Simple way to "fix" this: never use less children for rendering than for 3DView!

@Sergey Sharybin (sergey) reassigning this to you, since I’d like to have your feelings on the issue before diving deeper into ugly particle code. :/

There shouldn't be a parallel scene update at the same time if one renders with locked interface and/or fullscreen render. If that configuration still crashes, think it worth investigating why.

@Sergey Sharybin (sergey) can confirm the crash still happens when trying to render with locked UI *and* full screen… Also happens with fixed single-thread rendering, and -t 1 option

Not much i can add here. This isn't a regression, and the code is quite fragile and difficult to follow. Not something i want to be digging into.

Would rather facilitate the new node-based particles replacement instead! :)

Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".Jan 16 2020, 2:43 PM

Problem still seen in blender 2.83.