Mesh imported from alembic crashes later #50263

Closed
opened 2016-12-16 11:32:52 +01:00 by Jordan Hueckstaedt · 8 comments

System Information
Running: Windows 10 x64 with a gtx 1080 and plenty of ram.

Blender Version
2.78a

Alembic mesh created from "Quill" for Oculus frequently crashes in Blender. I'm not sure if Quill is creating bad geometry, or if Blender is behaving poorly, but I suspect Blender is at fault.
degenerate_crash.blend - has .abc file imported and relevant mesh isolated.
degenerate_crash.abc - source .abc file

Exact steps for others to reproduce the error
Here is some of the bad behavior I'm seeing:

  • Open the blend file.

  • Run the "separate" op.

  • Choose "Loose Parts"

  • Crashes with Error: EXCEPTION_ACCESS_VIOLATION
    Not all mesh from Quill exhibit this crash, but the one attached does.

  • Open the blend file.

  • Run "degenerate dissolve" op.

  • Crashes with Error: EXCEPTION_ACCESS_VIOLATION
    All Quill meshes that I've tested crash Blender doing this.

I think the issue lies with Blender. Maya doesn't seem to have any issue with this abc. If I exporting the mesh again from Maya -> Blender, Blender no longer crashes. It is possible that Maya fixes a problem with the mesh, or there is something unexpected in the way Quill is creating the Alembic file.

While the mesh does appear to have degenerate geometry (uv unwrapping it creates some very odd results), I'm not sure if this is a result of the import process or if it's in the actual abc file.

**System Information** Running: Windows 10 x64 with a gtx 1080 and plenty of ram. **Blender Version** 2.78a Alembic mesh created from "Quill" for Oculus frequently crashes in Blender. I'm not sure if Quill is creating bad geometry, or if Blender is behaving poorly, but I suspect Blender is at fault. [degenerate_crash.blend](https://archive.blender.org/developer/F418505/degenerate_crash.blend) - has .abc file imported and relevant mesh isolated. [degenerate_crash.abc](https://archive.blender.org/developer/F418503/degenerate_crash.abc) - source .abc file **Exact steps for others to reproduce the error** Here is some of the bad behavior I'm seeing: - > Open the blend file. - > Run the "separate" op. - > Choose "Loose Parts" - > Crashes with Error: EXCEPTION_ACCESS_VIOLATION Not all mesh from Quill exhibit this crash, but the one attached does. - > Open the blend file. - > Run "degenerate dissolve" op. - > Crashes with Error: EXCEPTION_ACCESS_VIOLATION All Quill meshes that I've tested crash Blender doing this. I think the issue lies with Blender. Maya doesn't seem to have any issue with this abc. If I exporting the mesh again from Maya -> Blender, Blender no longer crashes. It is possible that Maya fixes a problem with the mesh, or there is something unexpected in the way Quill is creating the Alembic file. While the mesh does appear to have degenerate geometry (uv unwrapping it creates some very odd results), I'm not sure if this is a result of the import process or if it's in the actual abc file.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @assumptionsoup

Added subscriber: @assumptionsoup

Added subscribers: @kevindietrich, @mont29

Added subscribers: @kevindietrich, @mont29
Kévin Dietrich was assigned by Bastien Montagne 2016-12-16 18:05:46 +01:00

@kevindietrich think you should call BKE_mesh_validate from importer (as we usually do in py add-ons importers), to ensure we have valid mesh data in the end?

@kevindietrich think you should call BKE_mesh_validate from importer (as we usually do in py add-ons importers), to ensure we have valid mesh data in the end?

@mont29, since Alembic can store hundreds of objects and since BKE_mesh_validate can slow down the import process, it is not called directly, but there is an option in the import settings for it.

@assumptionsoup, could you try importing the file with the "Validate Meshes" option checked?

@mont29, since Alembic can store hundreds of objects and since `BKE_mesh_validate` can slow down the import process, it is not called directly, but there is an option in the import settings for it. @assumptionsoup, could you try importing the file with the "Validate Meshes" option checked?

Oh awesome! That check box seems to fix the problem. My models are small enough I don't even notice a slow down checking it. UV unwrapping the model no longer produces bizarre results, and separate/dissolve degenerates no longer crash Blender!

Thanks guys!

Oh awesome! That check box seems to fix the problem. My models are small enough I don't even notice a slow down checking it. UV unwrapping the model no longer produces bizarre results, and separate/dissolve degenerates no longer crash Blender! Thanks guys!

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

I guess we can close this since the issue appears to be resolved.

I guess we can close this since the issue appears to be resolved.
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
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#50263
No description provided.