Crash when editing 'Resolution' value of 'Point Density' node #60960

New Issue

Sam Walker · 2019-01-28T23:40:44+01:00

Sam Walker commented

2019-01-28 23:40:44 +01:00

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: 001414fb2f
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

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

Point Density Crash 01a.blend

**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** - Open supplied '.blend' - Enable Cycles viewport rendering for the left-hand window. - Select 'Cube' object to view its material in the right-hand window's node-editor. - Edit the 'Resolution' parameter of the 'Point Density' node. [Point Density Crash 01a.blend](https://archive.blender.org/developer/F6436729/Point_Density_Crash_01a.blend)

Sam Walker commented

2019-01-28 23:40:44 +01:00

Added subscriber: @Hexbob6

Philipp Oeser commented

2019-01-29 12:59:28 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-01-29 12:59:28 +01:00

Cannot reproduce a crash here...

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

Marking as incomplete until we have that tried...

Cannot reproduce a crash here... Since e6acb4fba0 is rather "old", could you try in a new build? Marking as incomplete until we have that tried...

Sam Walker commented

2019-01-30 12:53:53 +01:00

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

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.

Jacques Lucke commented

2019-03-14 16:35:44 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-03-14 16:35:44 +01:00

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.

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.

Sam Walker commented

2019-03-17 22:17:44 +01:00

Have just tested in 52a7636c29 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 001414fb2f ) still occurs, with the console output being...

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7BE0DC914
Error   : EXCEPTION_ACCESS_VIOLATION
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.

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... ``` Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF7BE0DC914 Error : EXCEPTION_ACCESS_VIOLATION 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 commented

2019-03-27 12:48:53 +01:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2019-03-27 12:48:53 +01:00

Philipp Oeser self-assigned this 2019-03-27 12:48:53 +01:00

Philipp Oeser commented

2019-03-27 12:48:53 +01:00

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

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash when editing 'Resolution' value of 'Point Density' node #60960