Crash due to memory leak when CPU rendering in Eevee #55983

New Issue

Tom M · 2018-07-15T14:40:16+02:00

Tom M commented

2018-07-15 14:40:16 +02:00

System Information
Ubuntu Linux 16.04 64-bit, Fedora 27, Win 10
Intel HD 4000 graphics, i7, 16 GB ram

Blender Version
Broken version: 2.80 (sub 20), branch: blender2.8, commit date: 2018-07-13 23:37, hash: 19a55b5a00, type: Release
build date: 2018-07-14, 01:23:24
platform: Linux Crash is found with all three OS's.
Worked: (optional)

Short description of error
The latest versions of 2.80.20 for Linux and Windows crash due to a memory leak after CPU rendering enough frames, about 160 frames with a large scene having a 16K HDRI background. Even rendering the default cube scene without a background will crash Blender though it takes more frames with simple scenes. The problem occurs with .png and .mkv outputs but not when rendering with Cycles, which has constant memory used. This behavior has been seen in daily builds for weeks or more.

Exact steps for others to reproduce the error
With the default scene, set a high end frame of about 2500. CPU render with Eevee and watch the free system RAM disappear. Eventually it will run out and crash Blender and/or the OS. My system doesn't have a dedicated graphics card so this crash may only occur with CPU rendering.

**System Information** Ubuntu Linux 16.04 64-bit, Fedora 27, Win 10 Intel HD 4000 graphics, i7, 16 GB ram **Blender Version** Broken version: 2.80 (sub 20), branch: blender2.8, commit date: 2018-07-13 23:37, hash: 19a55b5a007, type: Release build date: 2018-07-14, 01:23:24 platform: Linux Crash is found with all three OS's. Worked: (optional) **Short description of error** The latest versions of 2.80.20 for Linux and Windows crash due to a memory leak after CPU rendering enough frames, about 160 frames with a large scene having a 16K HDRI background. Even rendering the default cube scene without a background will crash Blender though it takes more frames with simple scenes. The problem occurs with .png and .mkv outputs but not when rendering with Cycles, which has constant memory used. This behavior has been seen in daily builds for weeks or more. **Exact steps for others to reproduce the error** With the default scene, set a high end frame of about 2500. CPU render with Eevee and watch the free system RAM disappear. Eventually it will run out and crash Blender and/or the OS. My system doesn't have a dedicated graphics card so this crash may only occur with CPU rendering.

Tom M commented

2018-07-15 14:40:16 +02:00

Added subscriber: @tlm-3

Bastien Montagne commented

2018-07-16 16:46:56 +02:00

Added subscribers: @fclem, @mont29

Clément Foucault was assigned by Bastien Montagne

2018-07-16 16:46:56 +02:00

Bastien Montagne commented

2018-07-16 16:46:56 +02:00

Can confirm the increasing mem usage here on linux, but this is not happening in Blender itself, not anywhere in user space afaict, so would suspect something fishy in the kernel space (GPU driver), maybe some missing release of some buffers? @fclem, think that one is for you too.

Bastien Montagne commented

2018-07-16 16:47:31 +02:00

PS: note that this is no CPU rendering, this is off-line GPU rendering ;)

Tom M commented

2018-07-23 06:15:56 +02:00

Changed status from 'Open' to: 'Resolved'

Tom M closed this issue

2018-07-23 06:15:56 +02:00

Tom M commented

2018-07-23 06:15:56 +02:00

Recent 2.8 builds, including build date: 2018-07-20 show stable memory use, so this task is closed.

@Bastien, Your comment inspired some experimentation and research.

Presently Eevee shows 10-15 times faster rendering than comparable Cycles rendering. During Eevee rendering this system shows only one CPU thread at 100% and the other seven at 5-10% for an average of about 20%. Perhaps there is room for improvement with multi-threaded rendering. When using the AMD OpenCL startup command, CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 blender, render speed nearly doubles and average CPU use jumps to about 30%.

In Linux on this system the free Intel Graphics Performance Analyzer (GPA) software does not report percent utilization for GPU, only for CPU. Therefore, whether Eevee is CPU or GPU bound is not conclusive.

According to Statista in the first quarter of 2018 Intel had a GPU market share of 66.6 percent. Passmark says Intel has an installed GPU base of 80% in 2018. (https:*www.cpubenchmark.net/market_share.html) In June 2018 the venerable HD 4000 was the most popular Intel graphics system among Steam respondents. (https:*store.steampowered.com/hwsurvey/videocard/) Clearly any speedup of rendering for Intel graphics would benefit many if not most Blender users. Thanks.

Recent 2.8 builds, including build date: 2018-07-20 show stable memory use, so this task is closed. @Bastien, Your comment inspired some experimentation and research. Presently Eevee shows 10-15 times faster rendering than comparable Cycles rendering. During Eevee rendering this system shows only one CPU thread at 100% and the other seven at 5-10% for an average of about 20%. Perhaps there is room for improvement with multi-threaded rendering. When using the AMD OpenCL startup command, CYCLES_OPENCL_SPLIT_KERNEL_TEST=1 blender, render speed nearly doubles and average CPU use jumps to about 30%. In Linux on this system the free Intel Graphics Performance Analyzer (GPA) software does not report percent utilization for GPU, only for CPU. Therefore, whether Eevee is CPU or GPU bound is not conclusive. According to Statista in the first quarter of 2018 Intel had a GPU market share of 66.6 percent. Passmark says Intel has an installed GPU base of 80% in 2018. (https:*www.cpubenchmark.net/market_share.html) In June 2018 the venerable HD 4000 was the most popular Intel graphics system among Steam respondents. (https:*store.steampowered.com/hwsurvey/videocard/) Clearly any speedup of rendering for Intel graphics would benefit many if not most Blender users. Thanks.

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 due to memory leak when CPU rendering in Eevee #55983