Search Issue Tracker

Fixed in 2020.1.X

Fixed in 2019.2.X, 2019.3.X

Votes

8

Found in

2019.2

2019.2.11f1

2019.3

2020.1

Issue ID

1196536

Regression

Yes

Player freezes when Alt + Tabing if Player is running in the background and is in Exclusive Fullscreen mode

Windows

-

Steps to reproduce:
1. Download the attached project
2. Build a Standalone player (add "SampleScene" to build settings)
3. Launch player
4. Alt + Tab to focus on a different program

Results: After 3-5 Alt + Tabs Player freezes

Reproduced with: 2020.1.0a12, 2019.3.0b10, 2019.2.11f1
Not reproducible with: 2018.4.12f1

Note:
- Issue reproducible with IL2CPP and mono backends
- Issue is reproducible if player's Fullscreen mode is set to Exclusive and Run in Background is enabled
- Issue is reproducible when UI element's transformation is modified
- Tested and reproduced on Window 10
- The issue is reproducible with Run in Background is disabled, but it is more harder to do it.

Comments (7)

  1. BenIVRE

    Mar 21, 2024 17:13

    Reproduces in 2022.3.21f1 on Mac builds with Exclusive Fullscreen and Run In Background enabled.

  2. pertiofesim

    Jan 30, 2020 21:34

    issue still occurs,
    GPU: rx 5700 xt
    drivers issue: adrenalin 20.01.04

  3. kickstep

    Dec 06, 2019 02:47

    According to Tautvydas-Zilys this will be fixed in 2019.3.16

    https://forum.unity.com/threads/exclusive-fullscreen-alt-tabbing-freeze.789119/

  4. kickstep

    Dec 06, 2019 00:44

    Just tested in 2019.2.15f1

    Issue is not fixed.

    Also seems to have some side-effect where it is changing windowing mode to Windowed before re-creating Exclusive Fullscreen context.

  5. DropNodes

    Nov 17, 2019 12:30

    Planned for 2019.3, well we kinda need it for 2019.2.x too :)

  6. Kamyker

    Nov 09, 2019 00:58

    Video of how to reproduce it using Paladins and attached project. I wasn't unable to get this bug using Alt+Tab but somehow that other game always made Unity player freeze

    https://youtu.be/OrhaM_K4fQs

  7. AlistairFP

    Nov 08, 2019 18:19

    We had this exact issue in Rust, we were forced to downgrade to the last known working version which was 2019.2.

Add comment

Log in to post comment