Crash when opening file with multiple windows on different, multiple GPUs #51584
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#51584
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
Windows 10 64bit
Intel i5 3550 (with Intel HD Graphics 2500 integrated GPU, using built-in driver provided by Windows)
AMD Radeon RX480 4GB (with Radeon Software 17.5.2)
Blender Version
Broken: 2.78c official and recent builds
Short description of error
The bug requires opening a file which has saved in its configuration multiple windows on more than one display. If the second display is connected to a different GPU than the one used for the primary display, blender will crash upon opening the file. This issue may be driver-related and be triggered only on specific GPU/OS/Driver configurations.
Exact steps for others to reproduce the error
Alternatively, open the attached .blend file to trigger this bug.
multiple_windows_crash_test.blend
Workaround
The file can be successfully opened if there is only one active display connected on a single GPU.
Changed status to: 'Open'
Added subscriber: @s12a
Update: Blender does not crash if the primary display is on the integrated Intel GPU and the secondary display is on the AMD GPU.
I had to resave the file so that both windows are still opened on different displays upon opening.
This points to a driver issue.
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
This is indeed most certainly a driver issue… First thing you may try is to use Intel's official drivers instead of windows-provided ones, which are known to be even older and crappier than Intel's ones!
Beside that point, afraid we can't help you really here, this is totally out of our control, and until proven otherwise, not a Blender bug ;)