Page MenuHome

Crash when opening file with multiple windows on different, multiple GPUs
Closed, InvalidPublic

Description

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

  1. Shift-drag a corner of the 3d viewport to create a new window
  2. Move the new window to a secondary display connected to a second GPU of a different vendor than that of the first GPU
  3. Save file
  4. Exit Blender
  5. Reopen the file
  6. Blender will crash.

Alternatively, open the attached .blend file to trigger this bug.

Workaround
The file can be successfully opened if there is only one active display connected on a single GPU.

Event Timeline

s12a (s12a) updated the task description. (Show Details)May 22 2017, 8:48 AM

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.

Bastien Montagne (mont29) changed the task status from Unknown Status to Invalid.May 29 2017, 12:38 PM
Bastien Montagne (mont29) claimed this task.

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 ;)