blender 4..3 alpha Still unresponsive and unable to open #126812
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#126812
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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-10.0.19041-SP0 64 位
Graphics card: Intel(R) Iris(R) Xe Graphics Intel 4.6.0 - Build 31.0.101.5388
Blender Version
Broken: blender 4.3 alpha (since Aug 21)
Worked: blender 4.3 alpha (since Aug 19)
Short description of error
Still unresponsive and unable to open
Exact steps for others to reproduce the error
Unable to open blender
Hi, thanks for the report. Does it work if you launch blender from
blender_factory_startup.cmd
orblender_debug_gpu_glitchworkaround.cmd
batch file?Also, are you sure intel igpu is used? Do you have dedicated graphics in system?
Yes, I'm sure,my computer doesn't have another monitor,The logs log Error opening HIP dynamic library,Oh, I forgot to mention that Blender 4.1 version can run normally on my computer, but 4.3alpha doesn't work. It keeps showing no response and can't be opened
So this is failing with
blender_factory_startup.cmd
too?Can you check eventviewer or reliability monitor after blender fails to open. They might have reported relevant error.
yes,blender_factory_startup.cmd also failed , The reliability monitor shows that it stops interacting with Windows and closes, Eventviewer displays source application hang, event ID (E) 1002, task category (Y) 101.
The reliability monitor displays as follows
源
Blender
摘要
Stopped responding and was closed
日期
2024/8/28 7:47
状态
已发送报告
描述
A problem caused this program to stop interacting with Windows.
错误的应用程序路径: D:\blender-4.3.0-alpha+main.bb24677a76ce-windows.amd64-release\blender.exe
问题签名
问题事件名称: AppHangB1
Application Name: blender.exe
Application Version: 4.3.0.0
Application Timestamp: 66cd3055
Hang Signature: e94e
Hang Type: 134217728
OS 版本: 10.0.19045.2.0.0.768.99
区域设置 ID: 2052
Additional Hang Signature 1: e94ec99d284470103d30484181309791
Additional Hang Signature 2: 7b78
Additional Hang Signature 3: 7b78aaac82d6ed132c3c12166d991f12
Additional Hang Signature 4: e94e
Additional Hang Signature 5: e94ec99d284470103d30484181309791
Additional Hang Signature 6: 7b78
Additional Hang Signature 7: 7b78aaac82d6ed132c3c12166d991f12
关于该问题的额外信息
存储段 ID: de735f767f0d3b586b0fbad85d66c427 (1949982602117432359)
Hello, I tried to open blender 4.3alpha uploaded on August 19th today and it worked fine, but I couldn't open alpha uploaded from August 21st to 27th ,
Thanks. Can you share the hash of last working and first bad blender build?
Random guess, could it be due to the change on library side?:
bb7ae0e107
Hello, I guess it hasn't been working since August 21st. The 4.3alpha I tested on August 15th, 16th, 17th, 19th, and uploaded on August 19th works normally without any problems. Currently, the 8.21st and 8.27alphas I have tested cannot be opened
Thanks. I do not have anything to add further so resetting the status
Hi @yeye , do you have any plugins enabled? Are you unzipping blender directly over your existing installation or to a new fresh directory? It could be possible that some plugins are trying to connect the internet and caused blender to hang.
@ChengduLittleA No, I didn't have the chance to enable the plugin because I couldn't even open Blender. I just unzipped Blender directly over your existing installation
@yeye please unzip to a new place. It's possible that your old installation had plugin enabled and it will stay in the same scripts directory if you unzip over the old version.
@ChengduLittleA Hello, I tried to unzip to a new directory, but it still doesn't work. I can't open it
I confirm this is happening since
86e9254a63
on my A770.It's hanging in glLinkProgram. Maybe this can be mitigated from the application side but it shouldn't hang in the driver like it currently does. I've reported the issue to the driver team.