Properties Editor -> Material Tab -> Cycles auto renders icon which crashes blender when the material uses up too much ram #46001

New Issue

Carlo Andreacchio · 2015-09-03T08:40:34+02:00

Carlo Andreacchio commented

2015-09-03 08:40:34 +02:00

System Information
Windows 7 x64 GTX580, 16gb ram

Blender Version
Broken: 90f6675

Short description of error
Pretty much it is hard for artists to manipulate a objects material easily without the auto preview icon being fired off... Which poses a problem when dealing with large textures on low ram machines (look at the 42k resolution bugs I have been reporting :) )

Exact steps for others to reproduce the error

open up previously uploaded file F170781 on a low ram machine (12gb or 16gb should still crash)
open up node editor whilst keeping the material tab open
disconnect the image texture and reconnect
CRASH!

**System Information** Windows 7 x64 GTX580, 16gb ram **Blender Version** Broken: 90f6675 **Short description of error** Pretty much it is hard for artists to manipulate a objects material easily without the auto preview icon being fired off... Which poses a problem when dealing with large textures on low ram machines (look at the 42k resolution bugs I have been reporting :) ) **Exact steps for others to reproduce the error** 1. open up previously uploaded file [F170781](https://archive.blender.org/developer/F170781/42ktest.blend) on a low ram machine (12gb or 16gb should still crash) 2. open up node editor whilst keeping the material tab open 3. disconnect the image texture and reconnect 4. CRASH!

Carlo Andreacchio commented

2015-09-03 08:40:34 +02:00

Changed status to: 'Open'

Carlo Andreacchio commented

2015-09-03 08:40:34 +02:00

Added subscriber: @candreacchio

Sergey Sharybin commented

2015-09-03 11:15:21 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-09-03 11:15:21 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-09-03 11:15:21 +02:00

Sergey Sharybin self-assigned this 2015-09-03 11:15:21 +02:00

Sergey Sharybin commented

2015-09-03 11:15:21 +02:00

If preview render is not possible, then final rendering is even likely to fail.. Surely it's always possible to improve memory usage or handle out-of-ram issues more gracefully, but wouldn't consider this a bug.

So thanks for the report, but considering it a TODO.

If preview render is not possible, then final rendering is even likely to fail.. Surely it's always possible to improve memory usage or handle out-of-ram issues more gracefully, but wouldn't consider this a bug. So thanks for the report, but considering it a TODO.

Carlo Andreacchio commented

2015-09-03 23:53:56 +02:00

The problem lies that we tend not to have loads of high ram machines around... we tend to render off the ec2 which have the high amounts of ram... the artists still have to work on their low ram machines.

Understand that this isnt a big priority, just wanted flag it for the future.

The problem lies that we tend not to have loads of high ram machines around... we tend to render off the ec2 which have the high amounts of ram... the artists still have to work on their low ram machines. Understand that this isnt a big priority, just wanted flag it for the future.

Sergey Sharybin commented

2015-09-04 09:46:39 +02:00

It's more like a known problem which i've already tried to improve by avoiding having OIIO communication happening for previews.

Ideally, previews could share the same image pixels datablock, but in practice it's a bit tricky because Cycles might need to have different alignment than Blender is doing, plus user counter becomes more of a problem.

Also, out of memory can happen in other areas than texture loading. Additionally, OOM killer on linux can kill Blender before code itself will detect it run out of memory.

In any case, if you're building Blender yourself you might be interested to check D1502.

It's more like a known problem which i've already tried to improve by avoiding having OIIO communication happening for previews. Ideally, previews could share the same image pixels datablock, but in practice it's a bit tricky because Cycles might need to have different alignment than Blender is doing, plus user counter becomes more of a problem. Also, out of memory can happen in other areas than texture loading. Additionally, OOM killer on linux can kill Blender before code itself will detect it run out of memory. In any case, if you're building Blender yourself you might be interested to check [D1502](https://archive.blender.org/developer/D1502).

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

Properties Editor -> Material Tab -> Cycles auto renders icon which crashes blender when the material uses up too much ram #46001