Possible memory leak #55157

Closed
opened 2018-05-22 21:01:54 +02:00 by Artur · 4 comments

System Information
Windows 10 home 64b
Ryzen 2700x
32GB RAM DDR4 GoodRam 3000Mhz
SSD Samsung 960PRO 250 GB
MSI Gaming X GeForce 1060 6GB , driver ver. 391.35 from nVidia

Blender Version
Broken: 2.79 master branch, 2018-05-15 17:37, hash: 4461be1, branch: 2.8
Worked: (optional)

Possible memory leak. Very different render times with no changes to scene.

Exact steps for others to reproduce the error
With scenes whose memory usage is close to the memory capacity of my video card (4.5GB of my 6 GB) I got very different render times with same settings with hybrid rendering.
I was trying to get best tiles size setting for new scene of archviz for my clients. I opened scene, set tiles size to 32x32 and I got render time of 42 minutes. Then I changed tile size to 16 and I hit render button - 1 hour 21 minutes. Then by accident I used again 32x32 instead of 64x64 and I got 1 hour and 21 minutes render time - almost twice the time of first render. Nothing changed - camera, samplec etc. I can reproduce it with every scene with 4,5GB or more of memory peak.

**System Information** Windows 10 home 64b Ryzen 2700x 32GB RAM DDR4 GoodRam 3000Mhz SSD Samsung 960PRO 250 GB MSI Gaming X GeForce 1060 6GB , driver ver. 391.35 from nVidia **Blender Version** Broken: 2.79 master branch, 2018-05-15 17:37, hash: 4461be1, branch: 2.8 Worked: (optional) Possible memory leak. Very different render times with no changes to scene. **Exact steps for others to reproduce the error** With scenes whose memory usage is close to the memory capacity of my video card (4.5GB of my 6 GB) I got very different render times with same settings with hybrid rendering. I was trying to get best tiles size setting for new scene of archviz for my clients. I opened scene, set tiles size to 32x32 and I got render time of 42 minutes. Then I changed tile size to 16 and I hit render button - 1 hour 21 minutes. Then by accident I used again 32x32 instead of 64x64 and I got 1 hour and 21 minutes render time - almost twice the time of first render. Nothing changed - camera, samplec etc. I can reproduce it with every scene with 4,5GB or more of memory peak.
Author

Added subscriber: @azjarosz

Added subscriber: @azjarosz

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2018-07-22 13:11:47 +02:00

We’d need much, much more info to investigate this, provided there is indeed any issue here. The GPU is not only used for rendering, it still has to draw the screen with blender in it. And drivers can also be part of the problem here…
So am sorry, but will archive the report for now.

We’d need much, much more info to investigate this, provided there is indeed any issue here. The GPU is not only used for rendering, it still has to draw the screen with blender in it. And drivers can also be part of the problem here… So am sorry, but will archive the report for now.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#55157
No description provided.