Attached file imported with new OBJ importer later crashes on edge subdivision #103649
Labels
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#103649
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system:Windows 10
Graphics card:Geforce GTX
Blender Version
3.4
Short description of error
Crash on subdividing a mesh which is imported with new obj importer
(Mesh corruption is the reason I think)
Exact steps for others to reproduce the errora
Subdividefrom context menu (Right click)stage2.obj
blender.crash.txt
Added subscriber: @generalkenobi2
Added subscriber: @mod_moder
Changed status from 'Needs Triage' to: 'Needs User Info'
Hello, please, add some infor about your system and blender version:
This comment was removed by @generalkenobi2
system-info.txt
I've attached the sys-info
Thank you, though I meant the information for the report header. It's usually enough
Am I still missing info?
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
Okay, thanks for the system details. Now about the file. Can you attach an example where you can confirm the failure?
stage2.obj
Changed status from 'Needs User Info' to: 'Needs Triage'
Thank you. I checked and can't confirm.
I tested the model import and division in both today's debug build and the old regular build. I have a suspicion that it's either just out of memory or related to the render hardware.
How can I tell if im out of RAM, it crashes instantly and can't see it in task manager
Added subscribers: @aras_p, @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Hi, thanks for the report. Can repro the crash if obj file is imported with new C++ importer.
Looks like importing through it generates corrupted mesh (got loads of error message after running mesh.validate )
This does not happen on importing with legacy obj importer.
@aras_p , any idea what's causing this?
One difference I noticed is: new importer has not included edge creases
Blender crashes on edge subdivisionto Attached file imported with new OBJ importer later crashes on edge subdivisionChanged status from 'Needs Developer To Reproduce' to: 'Confirmed'
Looks like the OBJ file is produced from Blender itself. Can you also attach the original .blend file that you exported this model from? It seems that the OBJ file contains some "invalid mesh data" (duplicate faces, etc.), but I'm wondering how they got there in the first place.
From what I can tell, the repro OBJ file is invalid (duplicate faces etc.). The "validate option" is off in the new OBJ importer by default (following what is done with USD/Alembic), since validation has quite a lot of overhead. With validate option on, the crash does not happen.
The user never replied how they got the invalid OBJ file in the first place, so I'm thinking of closing this.