Blender crashes on startup if a large USD file is attached to the scene #105861
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#105861
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, Windows 11
Graphics card: GeForce RTX 1660 (Win 10), GeForce RTX 3060 (Win 11)
Blender Version
Broken: 3.3.1; 3.3.4; 3.4.1; 3.5 beta
Worked: not found
Short description of error
There are several Blender files created at different times. The files are scenes into which a file of the usd format is connected through the "MeshSequenceCache" modifier. If the usd file size exceeds a certain size, then with a high degree of probability, almost always, Blender will crash on startup.
At the moment, this situation occurs in the scene, to which the usd file is connected, about 1 GB in size.
The following method is used as a temporary solution. First, a file is launched that is either smaller or does not have a usd file attached. Then from the running program through the file-open the desired file is launched
Exact steps for others to reproduce the error
Attach a ~1 GB USB file to the scene using a modifier "MeshSequenceCache"
I created a USD file of just over 1GB.
For this I exported 2 Cubes that were subdivided 10 times.
I attached it by using the "MeshSequenceCache" modifier, saved and reopened a few times the .blend file, but I can't replicate the problem.
Please open Blender's installation directory and double click on the
blender_debug_gpu.cmd. This will start Blender in debug mode and create log files.Try to reproduce the error again.
Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information.
Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop.
Please also upload the crash log located in
C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt(or simply type%TEMP%into the path bar of the Windows Explorer).Crash in
usdBlender__pxrReserved__::ArResolver::_GetAssetInfo.It doesn't seem to be really related to memory. It seems to be a problem with the USD file. (Perhaps corrupted?)
If you could simply simplify the USD file somehow, and upload it here, that would allow confirmation of the report and proceed with the correction.
I was unable to send the file through the site. Can you download it from disk?
https://drive.google.com/file/d/1PGJgl5YiJ49se4oN21T97RmtBiOv4F6Z/view?usp=sharing
The file is an animation export from Maya
If I import this file into a new project, then no error occurs
I'll add to the above. Perhaps the error is somehow related to changing the file and changing the names of objects in it.
I will describe the process of my current work, in which an error occurs. The animator creates an animation of objects in Maya, after which the scene is exported in usd format. I am importing the usd file into the scene in blender for further work.
When the animator makes some changes to the animation, he exports the scene to a new usd file. I, in turn, replace the path to the old file with the new one in the modifier settings.
I checked with the animator whether new objects can be added and old ones can be added in the process of his work, and they confirmed to me that this is possible.
I had a guess. that an error can occur if the blender does not find information about the object in the usd file due to the fact that in the previous version of the file that was used during import, the objects had a different name
In version 3.5 the process looks more stable. Errors occurred during rendering, but not systemically and rarely.