Crash when changing preview monitor after disconnecting monitor

HDSQ.mid · May 26, 2021, 5:58am

What is your operating system?
Windows 10

What is your Shotcut version (see Help > About Shotcut)? Is it 32-bit?
21.05.18 64-bit

Can you repeat the problem? If so, what are the steps?
(Please be specific and use the names as seen in Shotcut, preferably English. Include a screenshot or screen recording if you can. Also, you can attach logs from either View > Application Log or right-click a job and choose View Log.)

Have Shotcut running with a preview on a secondary display
Disconnect the display (for me this was unplugging the USB-C dock that it was connected through)
Change the secondary display preview to None
Shotcut freezes and crashes

PaulusMaximus · May 26, 2021, 7:24am

Have you tried doing #3 before #2?

EDIT: I’m now on a USB-C Dock. If I set W10 to “Extend” the monitor", I then put a SC window (keyframes in this case) on the secondary monitor, I then select “PC Screen Only” within W10, the secondary screen shuts off and the keyframes window is then moved automatically as top window (focus 0) on the first monitor, SC does not crash with this test.

I have also done the same with the entire SC application on a secondary, same procedure as above, no crash.

shotcut · May 26, 2021, 7:51pm

See related bug

github.com/mltframework/shotcut

Switching external monitors results in wrong position, crash etc.

opened 08:04PM - 18 Jul 19 UTC

Gizemquea

Shotcut 19.07.15 Windows 10 (broken on older versions too) In a setup with mu…ltiple monitors, switching between external monitors doesn't work reliably. My display setup is: [2][3] [1] were display 3 uses a separate graphics card. Resolutions are 1920x1080 on the external displays and 2736x1824 on internal display. When selecting an external monitor for the first time (or when restarting the application with an arbitrary external monitor set), the positioning "kind of" works as intended BUT 1.) screen nunbers are inconsistent between shotcut and windows: windows screen 1 -> shotcut screen 0 windows screen 2 -> shotcut screen 2 windows screen 3 -> shotcut screen 1 2.) switching from external monitor 1 to external monitor 2 will position video on screen 0 instead, trying to switch back to none in this state will KEEP a working full screen video display on screen 0 3.) switching from external monitor 1 to none will often result in monochrome video overlaying the whole shotcut window, rendering the UI useless (tool tips will still work) 4.) switching from external monitor 2 to external monitor 1 will always result in wrongly positioned video overlaying part of shotcut screen 0 (the x-coordinate seems right, but y-coordinate is at top of screen 0. 5.) switching back from external monitor 1 to external monitor 2 will result in wrongly positioned video INSIDE a black box overlaying the left side of screen 0 (right border of the black box seems right, but video size is wrong) 6.) switching back to external monitor 1 will SHRINK the video (no black box), top left corner of video overly is the same as in 4. x/y size of video is exactly 1/2 of desired display size (960x540) 7.) switching external monitor back and forth repeatedly while video is playing will always result in a crash (application closes) 8.) running shotcut on the display using the external graphics card and switching external monitors betwen displays of the internal graphics doesn't behave much better - I'll spare you the details... 9.) now for the good news: you don't need an external graphics card to reproduce a crash. Removing windows screen 3 (including the whole hardware) completely from my setup and positioning screens of the internal graphics card side-by-side will still crash shotcut when trying to switch from etxternal monitor 1 to none while playing video. If video is not playing, it will produce the same result as in 3. I observed similar behaviour on three other systems with completely different hardware, including a configuration where the integrated graphics can handle three monitors simultaneously.

In short, it’s complicated, and I have been unable to fix it.