Blender Crashes while using Quadriflow while preserving curvature #69866

Closed
opened 2019-09-14 03:41:34 +02:00 by Ahmad Bilal · 13 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006

Blender Version
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-13 15:37, hash: 92736a7b75
Worked: (optional)

Quadriflow works just fine in most other modes (haven't really 100% nitpicked it yet) .. but I noticed that blender crashes way more than acceptable no of times if I use the setting 'Use Mesh Curvature' together with Mesh Boundary and Preserve Sharp settings. Sometimes it works okay, but most of the times it just crashes around 30%-40% remesh completion progress.

Turning off 'Use Mesh Curvature' brings about stability.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006 **Blender Version** Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-13 15:37, hash: `92736a7b75` Worked: (optional) Quadriflow works just fine in most other modes (haven't really 100% nitpicked it yet) .. but I noticed that blender crashes way more than acceptable no of times if I use the setting 'Use Mesh Curvature' together with Mesh Boundary and Preserve Sharp settings. Sometimes it works okay, but most of the times it just crashes around 30%-40% remesh completion progress. Turning off 'Use Mesh Curvature' brings about stability.
Author

Added subscriber: @SomeAB

Added subscriber: @SomeAB

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Need steps to reproduce this. Just stating that it is a problem with no reproduction steps is not helpful.

Need steps to reproduce this. Just stating that it is a problem with no reproduction steps is not helpful.
Author

I thought what I wrote should have been clear enough. But here anyway:

  1. Take a mesh above 10k vertices (I noticed this crash doesn't happen on low poly models)
  2. Choose to Quadriflow Remesh in any mode (I use Edge mode mostly)
  3. Select the checkbox for 'Preserve Sharp' + 'Preserve Mesh Boundary' and (lastly and most importantly) 'Use Mesh Curvature'
  4. Press 'Ok' to start remeshing process
  5. Crash
I thought what I wrote should have been clear enough. But here anyway: 1. Take a mesh above 10k vertices (I noticed this crash doesn't happen on low poly models) 2. Choose to Quadriflow Remesh in any mode (I use Edge mode mostly) 3. Select the checkbox for 'Preserve Sharp' + 'Preserve Mesh Boundary' and (lastly and most importantly) 'Use Mesh Curvature' 4. Press 'Ok' to start remeshing process 5. Crash
Author

just checked the latest build .. (blender-2.81-9609840b5ea1-windows64). now there is no crash when 'Use Mesh Curvature' is checked.

But the performance has gone down way down for me. To give you an idea, earlier I had a scene open with 1.8 million tris, and a typical 30K faces model would get remeshed into a similar sized mesh (about 30k also) in under 1 minute while that scene was open (in the build version mentioned in the first post). Now in a clean file, with about450k tris, I can't remesh a 80k faces model model into a similar sized mesh (60k faces) in even 15 minutes!

I'm pretty sure that there is a memory overflow issue somewhere. Since now blender is taking 5 to 6 GB of RAM and still can't remesh that 60k mesh in even 15 minutes.

Let me know, if you need more information from my side.

just checked the latest build .. (blender-2.81-9609840b5ea1-windows64). now there is no crash when 'Use Mesh Curvature' is checked. But the performance has gone down way down for me. To give you an idea, earlier I had a scene open with **1.8 million tris**, and a typical **30K faces model** would get remeshed into a similar sized mesh (about 30k also) in under **1 minute** while that scene was open (in the build version mentioned in the first post). Now in a clean file, with about**450k tris**, I can't remesh a **80k faces model** model into a similar sized mesh (60k faces) in even 15 minutes! I'm pretty sure that there is a memory overflow issue somewhere. Since now blender is taking 5 to 6 GB of RAM and still can't remesh that 60k mesh in even 15 minutes. Let me know, if you need more information from my side.
Author

Dropped back to blender-2.81-92736a7b7592-windows64 .. and though I'm able to complete my remeshing attempts (same 450k tris file) .. it is taking me longer than before (yet still less than latest build) .. about 5-6 minutes.

Edit 1: Yup, it definitely seems that something is going on behind the scene. I made a clean file with only 1 object of 110k faces/218k tris -- > 80k faces. tried to remesh it thrice (once in previous 450k file) .. and even after 20-30 minutes, it doesn't get done (despite of using 6.5GB of RAM) .. and blender crashed each time.

Not only blender, but discord and few mozilla firefox tabs crashed as well.

Edit 2: After spending the whole morning toying with it. I noticed something interesting:

  1. I took my 110k faces model .. voxel remeshed it first (at 0.006 setting) ..
  2. and it became 530k tris
  3. After that I remeshed it using Quadriflow, but this time the edge length was set to 0.012 (instead of 0.01)
  4. The 530k got remeshed into 110k tris/55k faces in less than 30 seconds. and blender memory usage howered around 1GB for most of the time, and peaked at 2.7GB

Edit 3: Day 2, and after a lot more tingling with the settings:

From what I'm seeing, using the setting of edge length = 0.012 works most of the time, while 0.01 breaks things many a times.

Dropped back to blender-2.81-92736a7b7592-windows64 .. and though I'm able to complete my remeshing attempts (same 450k tris file) .. it is taking me longer than before (yet still less than latest build) .. about 5-6 minutes. Edit 1: Yup, it definitely seems that something is going on behind the scene. I made a clean file with only 1 object of 110k faces/218k tris -- > 80k faces. tried to remesh it thrice (once in previous 450k file) .. and even after 20-30 minutes, it doesn't get done (despite of using 6.5GB of RAM) .. and blender crashed each time. Not only blender, but discord and few mozilla firefox tabs crashed as well. Edit 2: After spending the whole morning toying with it. I noticed something interesting: 1) I took my 110k faces model .. voxel remeshed it first (at 0.006 setting) .. 2) and it became 530k tris 3) After that I remeshed it using Quadriflow, but this time the edge length was set to 0.012 (instead of 0.01) 4) The 530k got remeshed into 110k tris/55k faces in less than 30 seconds. and blender memory usage howered around 1GB for most of the time, and peaked at 2.7GB Edit 3: Day 2, and after a lot more tingling with the settings: **From what I'm seeing, using the setting of edge length = 0.012 works most of the time, while 0.01 breaks things many a times.**
Author

@ZedDB any update?

@ZedDB any update?

I can't reproduce this issue on my test meshes. So unless you actually provide an example file there is nothing I can do.

I can't reproduce this issue on my test meshes. So unless you actually provide an example file there is nothing I can do.

Actually, could you see if you still get crashes if you change sound system backend to "Null" in the preferences? It seems like some people get sound crashes when running the operator for some reason.

Actually, could you see if you still get crashes if you change sound system backend to "Null" in the preferences? It seems like some people get sound crashes when running the operator for some reason.
Sebastian Parborg self-assigned this 2019-09-24 17:03:31 +02:00
Author

Okay, I will test the old version as well as the new version and let you know. And I will also make a minimal demo file for you.

Okay, I will test the old version as well as the new version and let you know. And I will also make a minimal demo file for you.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
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
3 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#69866
No description provided.