When having large textures, going to lookdev then back to cycles doubles the ram usage until you reset blender #67493

New Issue

Mehrbod Khademy · 2019-07-23T08:22:13+02:00

Mehrbod Khademy commented

2019-07-23 08:22:13 +02:00

16gb ddr3 ram
intel core i7 3775k
nvidia gtx 1050 ti (4gb vram)

Windows 10 64-bit

Nvidia gtx 1050 ti (4gb vram)

Release candidate 2
Broken: v 2.8 release candidate 2

When changing to lookdev when having large textures, ram usage went doubled, and going back to cycles made blender stop responding with a "cancel" on the top of render region, until i reset blender and it works again

Load large textures onto an object, preferably 800mb+ (16k~) then render in cycles, take note, go to lookdev, come back to cycles, the ram usage is doubled and cycles struggles to start rendering
(Couldn't send the blend files since attending it would be around 1.5gb)

16gb ddr3 ram intel core i7 3775k nvidia gtx 1050 ti (4gb vram) Windows 10 64-bit Nvidia gtx 1050 ti (4gb vram) Release candidate 2 Broken: v 2.8 release candidate 2 When changing to lookdev when having large textures, ram usage went doubled, and going back to cycles made blender stop responding with a "cancel" on the top of render region, until i reset blender and it works again Load large textures onto an object, preferably 800mb+ (16k~) then render in cycles, take note, go to lookdev, come back to cycles, the ram usage is doubled and cycles struggles to start rendering (Couldn't send the blend files since attending it would be around 1.5gb)

Mehrbod Khademy commented

2019-07-23 08:22:13 +02:00

Added subscriber: @Mehrbod

Germano Cavalcante commented

2019-07-23 22:20:21 +02:00

Added subscribers: @brecht, @mano-wii

Germano Cavalcante commented

2019-07-23 22:20:22 +02:00

Most likely there is no memory leak, but it is some kind of cache that is initialized only when the texture is used.
Cycles handles textures differently from Blender in general. So it has its own cache.
But that is my assumption. @brecht, what do you think?

Most likely there is no memory leak, but it is some kind of cache that is initialized only when the texture is used. Cycles handles textures differently from Blender in general. So it has its own cache. But that is my assumption. @brecht, what do you think?

Brecht Van Lommel commented

2019-07-25 01:44:17 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-07-25 01:44:17 +02:00

Brecht Van Lommel self-assigned this 2019-07-25 01:44:17 +02:00

Brecht Van Lommel commented

2019-07-25 01:44:17 +02:00

This is a limitation of texture memory management currently. Cycles is a separate renderer and will allocate the textures again.

In the future we can optimize this to perhaps automatically deallocate textures from LookDev when starting Cycles, but I would not consider this a bug.

This is a limitation of texture memory management currently. Cycles is a separate renderer and will allocate the textures again. In the future we can optimize this to perhaps automatically deallocate textures from LookDev when starting Cycles, but I would not consider this a bug.

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

When having large textures, going to lookdev then back to cycles doubles the ram usage until you reset blender #67493