Page MenuHome

Crash when editing 'Resolution' value of 'Point Density' node
Closed, ResolvedPublic


System Information
Operating system: Windows 10
Graphics card: Nvidia GTX 1070

Seperate system also tested...
Operating system: Windows 10
Graphics card: Nvidia GTX 1080Ti

Blender Version
Broken: 001414fb2f73
Worked: 2.79b release

Short description of error
Consistent crash if the 'Resolution' value of a Point Density node is altered whilst Cycles is performing a viewport render.

Exact steps for others to reproduce the error

  1. Open supplied '.blend'
  2. Enable Cycles viewport rendering for the left-hand window.
  3. Select 'Cube' object to view its material in the right-hand window's node-editor.
  4. Edit the 'Resolution' parameter of the 'Point Density' node.



Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Needs Information from User priority.

Cannot reproduce a crash here...

Since rBe6acb4fba094 is rather "old", could you try in a new build?

Marking as incomplete until we have that tried...

So it is! Have just downloaded 001414fb2f73 on a different machine to test and it is still causing a crash. Will update the task with the new details.

Cannot reproduce it in the current version either, please try again...
Is there any error message in the console?
Does this happen with CPU and GPU rendering?

The resolution does not update in the viewport in real time, but it does not crash.

Have just tested in 52a7636c2921 and no longer appear to be experiencing the crash, and the resolution does seem to be updating in the rendered viewport as expected.

I suppose it is unnecessary to delve deeper as the issue seems to be fixed in the latest release, however for the sake of documenting what happened, the crash in previous versions (for example 001414fb2f73 ) still occurs, with the console output being...

Address : 0x00007FF7BE0DC914
Module  : C:\Path\To\Blender\Build\blender-2.79.0-git.001414fb2f73-windows64\blender.exe

... just in case that is of relevance. The crash occurred when rendering both on the CPU and GPU.

Philipp Oeser (lichtwerk) claimed this task.

Since this seems to be fixed in master, I guess we can close this one...