Crash during render due to denoising
Closed, ArchivedPublic

Description

System Information
System 1:
OS: Windows 10 32-bit
CPU: Intel Atom Z3740 @1.33GHz
GPU: Intel HD Graphics (Integrated)
RAM: 2.00GB

System 2:
OS: Windows 7 Ultimate 64-bit SP1
CPU: AMD Athlon II X2 270 @2.3GHZ
GPU: ATI Radeon 7000 Graphics (Integrated)
RAM: 8.00GB
(Note: both systems are using a 32-bit build of Blender)

Drivers on both systems are up-to-date.

Blender Version
Broken: 2.79 5bd8ac9 32-bit build (the release version available on the blender.org website)

Short description of error
Blender crashes to desktop mid-render when attempting to perform a denoising operation. The console spits out "Error: EXCEPTION_ACCESS_VIOLATION", implying a problem with memory usage. Memory usage was roughly ~120.00M according to the info bar at the time of the crash. Task Manager reports that Blender was using ~250MB of RAM at the time of the crash, available RAM was ~500MB with plenty of virtual memory to spare.

If it is a memory problem how much memory should the denoising feature really be using?

This crash happens even on simple scenes such as the default startup scene, with render resolutions set to something really low (like 320x240 pixels) and using the smallest tile size possible (8x8), and when using only one thread. The render will complete normally with denosing disabled.

On System 2 the render completes normally with denoising. System 2's Task manager reported Blender was using ~250MB during the render.

Exact steps for others to reproduce the error
Render a scene via Cycles with denoising enabled.

Details

Type
Bug
LazyDodo (LazyDodo) triaged this task as Incomplete priority.Sep 30 2017, 1:16 AM

There is some work being done in this area in T52572 , can you confirm with a build from http;//builder.blender.org that the problem has been resolved?

@LazyDodo (LazyDodo)
The render seems to completes successfully with denoising on System 1 with the (at the time of this writing) latest 32-bit build from buildbot.

I'm still unsure as to how those CUDA errors mentioned in T52572 would have caused the crashes I'm experiencing.

LazyDodo (LazyDodo) closed this task as Archived.Sep 30 2017, 8:38 PM
LazyDodo (LazyDodo) claimed this task.

Well unless we have a way to reproduce that crash there is not much we can do, so for now i'm going to close this ticket, if the problem ever comes back, feel free to open this ticket again and attach a .blend file exhibiting the issue.

I've several systems at home, and noticed that Cycles crashed when I had the Denoise feature enabled on my Intel Atom laptop.

Specs of all my systems:
Nala (main desktop)
Windows 10 64-bit
i5-4590
8 GB RAM
GTX 960 2GB

Laptop
Windows 10 32-Bit
Intel Atom Z3735F
Intel HD
2 GB RAM

Desktop #2
Windows 7 64-bit
Intel Pentium J2900
Intel HD
4 GB RAM

The latest official builds of Blender 2.79 were used in all of the above systems. In narrowing down variables, I used Desktop #2 to find what is causing the Denoise feature to crash. With the 64-bit build of Blender, the render finished and the Denoise worked perfectly. Installing the 32-bit version of Blender, and rendering with the same file, Blender crashed as soon as Denoise was attempted. Disabling Denoise allows the render to finish. I can reasonably conclude that the 32-bit Blender build has the bug.

The file used is included below.