Freestyle excess memory usage? Crash #71281

Closed
opened 2019-11-02 06:27:23 +01:00 by Paul Hartsuyker · 4 comments

{F7939965}System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-10-31 19:29, hash: 78ad368d12
32GB memory on Motherboard
Worked: (optional)

Short description of error
Same scene that I have been trying to Render in Freestyle, (also fails in LANPR)
It is a large landscape, with characters, leaves, grass, fur, etc. 1920x1080px
Small slices (Render Region) shouldn't use the same amount of RAM and crash as the full scene

Exact steps for others to reproduce the error
Attempting to get a Line Render using Freestyle. I have successively reduced the Render Zone, as it crashes on the full scene, Crashed on 1/2 scene, 1/3 scene, and currently stuck in Freestyle: View map creation at 1/5 slice of the scene, using 97%-99% of available RAM?? It seems to be trying to make a View map of the entire scene, instead of just the subset slice. I was going to send it to a Render Farm to do in Tiles, but Freestyle doesn't seem to be conducive to using less memory on smaller subsets?? How to proceed??
Went to bed, checked three(3) hours later, CRASH. I gently complained on "Blender Today" and Dalai Felinto and Pablo Vasquez, both said it sounded like a bug, and submit it!! Line Rendering needs to work reliably.
I am attaching an example of the Render Region I am attempting to render with Freestyle, shown in MatCap on far left edge.

{[F7939965](https://archive.blender.org/developer/F7939965/2.82.1-GPU_11-04-2019_region-render.png)}**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-10-31 19:29, hash: `78ad368d12` 32GB memory on Motherboard Worked: (optional) **Short description of error** Same scene that I have been trying to Render in Freestyle, (also fails in LANPR) It is a large landscape, with characters, leaves, grass, fur, etc. 1920x1080px Small slices (Render Region) shouldn't use the same amount of RAM and crash as the full scene **Exact steps for others to reproduce the error** Attempting to get a Line Render using Freestyle. I have successively reduced the Render Zone, as it crashes on the full scene, Crashed on 1/2 scene, 1/3 scene, and currently stuck in Freestyle: View map creation at 1/5 slice of the scene, using 97%-99% of available RAM?? It seems to be trying to make a View map of the entire scene, instead of just the subset slice. I was going to send it to a Render Farm to do in Tiles, but Freestyle doesn't seem to be conducive to using less memory on smaller subsets?? How to proceed?? Went to bed, checked three(3) hours later, CRASH. I gently complained on "Blender Today" and Dalai Felinto and Pablo Vasquez, both said it sounded like a bug, and submit it!! Line Rendering needs to work reliably. I am attaching an example of the Render Region I am attempting to render with Freestyle, shown in MatCap on far left edge.

Added subscriber: @PaulHartsuyker

Added subscriber: @PaulHartsuyker

Closed as duplicate of #49141

Closed as duplicate of #49141

Added subscriber: @brecht

Added subscriber: @brecht

Freestyle is known to have poor memory usage and performance with a lot of geometry. While this could be optimized, Freestyle is no longer being actively developed and more likely is that LANPR will replace it.

In general, border render also does not mean only a subset of the scene can be rendered, because there are interactions with lines off screen as well.

Freestyle is known to have poor memory usage and performance with a lot of geometry. While this could be optimized, Freestyle is no longer being actively developed and more likely is that LANPR will replace it. In general, border render also does not mean only a subset of the scene can be rendered, because there are interactions with lines off screen as well.
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#71281
No description provided.