Crash on startup on older CPUs, due to unsupported instruction in USD libraries #97950
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#97950
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 build 19043.1645
Graphics card: Geforce 605 (latest compatible driver installed - OpenGL 4.6, no vulkan support)
Blender Version
Broken: 3.2 Alpha from April 29, 15:37:48 -
a1b21a3503-and any newer buildWorked: 3.2 Alpha from April 28, 22:25:22 -
308a12ac64Short description of error
Blender can't initialize. Blender's terminal flashes and closes with no error message when launching blender.exe.
Debug log is blank. No crash log writen on temp folder.
Exact steps for others to reproduce the error
Launch Blender from any automatic build newer than 3.2 alpha from April 28.
Note
I noticed FFmpeg 5.0 library files were implemented April 29 on daily builds. Also there is a commit this same day altering a manifest in a file of the windows builds. Don't know if any of this would contribute with this crash.
Blank debug log from newest 3.3 alpha:
blender_debug_output.txt
Added subscriber: @chimia
#97981 was marked as duplicate of this issue
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Thanks for the report. Probably same crash as stated in #97849 (Blender 3.2 gpu shader overlay crash)
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 inC:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt(or simply type%TEMP%into the path bar of the Windows Explorer).Hello! Tested again with version 3.2 beta built today - hash
a4c2060b91Same issue happening. GPU debug log is blank and also no crash log generated.
Old alpha from april 28 and Blender 3.1.2 are working fine.
blender_debug_output.txt
Added subscriber: @Cole-Marcus
Same. Just downloaded the latest Blender dev builds but the issue occurs again and again. I have uploaded my crash log below.
blender_debug_output.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
@Cole-Marcus, this error is the same as #97545 (EEVEE Viewport Shading crash (3.2.0 Alpha)) which has already been fixed by
aa34706aac.Please try the latest daily build: https://builder.blender.org/download/
Unfortunately the logs from @chimia do not provide any useful information to identify the problem.
Maybe if you run blender from the command line it can provide some information:
https://docs.blender.org/manual/en/2.79/render/workflows/command_line.html#ms-windows
Changed status from 'Needs User Info' to: 'Resolved'
This comment was removed by @Cole-Marcus
Good news! I installed the latest daily build and the issue does not occur anymore.
Changed status from 'Resolved' to: 'Needs User Info'
@Cole-Marcus , good to know that latest builds are not crashing in your system.
But I'll still wait for original reporter's reply if crash is resolved for them
Unfortunately the issue still running in the new build. Blank logs, no error message. #97981 shows the very same problem running on a different GPU, but same CPU model which has no AVX instructions support. The strange part is the old alpha runs perfectly. Something changed that day? I have no idea what is going wrong.
Added subscribers: @LazyDodo, @brecht
CC @LazyDodo. April 29 is when libraries were upgraded ({rBL62897}).
It's a little hard to diagnose without any log or other indication what the problem is, Is there anything in the windows event log from around the time of the crashes?
@chimia is there any chance you can give me a screenshot of the main screen of cpu-z ? Even better if you could click the Tools->Save Report as TXT button and attach the report it makes.
Found this on Windows Event Log{F13069255}
Blender Startup Crash.evtx
Also, Cpu-Z report
cpu-z.txt
Added subscribers: @makowalski, @dr.sybren
Well, this was fun to track down :)
Looks like USD emits an rdtscp instruction on both Windows+Linux .
I'm not sure if GCC substitutes it with a more appropriate instruction behind the scenes but MSVC definitely doesn't, a quick google says this raises our lower bar to Nehalem for intel and K8 hammer for AMD.
Unsure what we want to do here, an older commit used
QueryPerformanceCounteron windows which could work but doesn't help linux all that much.....cc: @dr.sybren , @makowalski
Impressive job! I would never catch that alone.
But thats kinda sad raise the lower bar, this CPU does a pretty decent job on modelling and sculpting. Even geometry nodes play well. :(
This issue was referenced by
018acc5688@LazyDodo, I think we can just go back to what USD 21.03 was doing. I created a patch since it was simpler than explaining how.
Added subscribers: @Alexander_Berg, @rjg
Changed status from 'Needs User Info' to: 'Confirmed'
Marking as high prio so we remember to commit updated libs for 3.2.
Crash: Fail to initialize Blender new alpha daily builds since April 29thto Crash on startup on older CPUs, due to unsupported instruction in USD librariesWindows libs have been updated for master and 3.2 , should be included in the next nightly build.
Confirmed. Solved issue in 3.2! Thank you @brecht !
And still impressed on how you tracked it down @LazyDodo ! :)
Changed status from 'Confirmed' to: 'Resolved'
Linux libs have been updated for master and 3.2, should be included in the next nightly build.