obj file opening crash #57951
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#57951
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
I5-8300H CPU
16GB RAM
Samsung 970 EVO 250 GB SSD
1TB HDD
1050 GPU 4GB
Blender Version
Broken: 2.79b *.obj opening
Short description of error
When I tried open a obj file (size ~500 mb or bigger) the blender collapsed. After the first, the blender randomly collapsed. I tired to reinstall many times, but didnt work.
Somebody have the same?
Thanks?
Added subscriber: @steinmann.vilmos
Added subscriber: @mont29
You are most certainly running out of RAM… but quiet impossible to say anything for sure without the file to reproduce the issue.
I am not sure, I checked the ram, and I used only half of the avaibale, and befor the OS reinstallin (win10 befor and now) I didnt have any problem, but thank for the help
Changed status from 'Open' to: 'Archived'
Well, memory display is not always accurate at instant time, and you also have to take into account fragmentation (such big OBJ is likely to try to assign huge arrays, ie. require huge amounts of contiguous memory).
Anyway, without anyway to reproduce from our end, am afraid we cannot do much, so will archive this report for now.