Maniphest T104093

dual monitor will sometimes cause blender to freeze
Needs Triage, Normal
Actions

Assigned To
None
Authored By
Hongyu Fu (HF)
Mon, Jan 23, 4:21 PM
Tags
  • BF Blender
Subscribers
Hongyu Fu (HF)
Richard Antalik (ISS)

Description

System Information
Operating system:win10
Graphics card:2080s

Blender Version
Broken: 3.4.1
Worked:

Short description of error
i have two monitors (4k and 2k) scrolling timeline or doing anything on one monitor and displaying cycles render viewport on the other monitor will sometimes cause blender to freeze forever

it is not specific to this scene it will freeze on all kinds of scenes, might be related to the muti-monitor bug i have been reporting https://developer.blender.org/T96248
here is a screenshot of what it looks like when freezing

Exact steps for others to reproduce the error
make some animation
have 2 monitors and use cycles rendered view on one monitor and scrolling timeline on the other monitor

Related Objects

Event Timeline

Hongyu Fu (HF) renamed this task from scrolling timeline will cause blender to freeze to dual monitor scrolling timeline will cause blender to freeze.Mon, Jan 23, 4:21 PM
Hongyu Fu (HF) created this task.
Hongyu Fu (HF) renamed this task from dual monitor scrolling timeline will cause blender to freeze to dual monitor will sometimes cause blender to freeze.Fri, Jan 27, 9:05 PM
Hongyu Fu (HF) updated the task description.
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).Tue, Jan 31, 2:54 AM

Could be related to previous report. Is this recent regression, or did this happen in previous versions too?

Hongyu Fu (HF) added a comment.Thu, Feb 2, 8:00 AM

I have not tried previous versions. Because of the dual monitor bug report, i havent used a proper 2 monitor set up until now.

I havent seen the problem from previous report but im not using 4k display as the cycles viewport anymore. Im only using a corner of a 2k screen

Richard Antalik (ISS) added a comment.Thu, Feb 2, 10:06 AM

Thanks for info. Now I am not sure if I understood it properly, but if you can no longer reproduce issue previously reported, please leave a comment there so it can be closed. If you are unsure, we will always appreciate re-checking.