Search Issue Tracker

Fixed in 2020.2

Fixed in 2018.4, 2019.4, 2020.1

Votes

0

Found in

2020.1.0a11

2020.1.0b4

2020.2

Issue ID

1231978

Regression

Yes

[Graphics] Game View Skybox flickers on resizing its Window with Frame Debugger enabled

Graphics - General

-

On resizing the Game View Window or changing the layout with the Frame Debugger Enabled the Game View Skybox flickers and the memory usage for the project temporarily increases significantly in Task Manager.
Refer to the attached Video.

Steps to Reproduce:
1. Create a New Project
2. Hierarchy > Right-click > 3D Object > Cube
3. Window > Analysis > Frame Debugger > Enable
4. Resize the Game View

Actual Result:
D3D11: Game View flickers and the skybox renders black on resizing
Vulkan: Game View flickers and completely turns white on resizing

Expected Result:
D3D11/Vulkan: Game View rendering should be unaffected by resizing

Occurring on:
2020.2.0a5, 2020.1.0b4, 2020.1.0a11

Working Fine on:
2020.1.0a10, 2019.3.7f1

Environment:
Windows 10 and macOS 10.14(Metal)

Note:
With Dx11 Project's memory usage increases only while resizing and stabilizes after some time.
Although, continuously resizing the Editor window leads to the memory usage reaching a certain threshold after which the Editor freezes and then crashes with the following error:
D3D11: Failed to create render texture primary DSV (error 0x80070057)

========== OUTPUTTING STACK TRACE ==================

ERROR: SymGetSymFromAddr64, GetLastError: 'Unknown error [-529697949]' (Address: 00007FF6240C0EC9)
0x00007FF6240C0EC9 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Unknown error [-529697949]' (Address: 00007FF626F8F570)
0x00007FF626F8F570 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Unknown error [-529697949]' (Address: 00007FF626F99D9C)
0x00007FF626F99D9C (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Unknown error [-529697949]' (Address: 00007FF626F9A188)
0x00007FF626F9A188 (Unity) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Unknown error [-529697949]' (Address: 00007FF624EFCE70)
0x00007FF624EFCE70 (Unity) (function-name not available)
0x00007FFC87687974 (KERNEL32) BaseThreadInitThunk
ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 00007FFC899AA261)
0x00007FFC899AA261 (ntdll) (function-name not available)

========== END OF STACKTRACE ===========

  1. Response avatar

    Resolution Note (fix version 2020.2):

    When the game view is resized we need to create a new render target for it. We have a temp render target manager for this (which is why mem consumption is increased momentarily, but stabilized with time as the manager does garbage collection). These temp render target creation events ended up creating noise in the frame debugger event stream which manifested as flickering. Fix is incoming.

  2. Response avatar

    Resolution Note (fix version 2020.1):

    When the game view is resized we need to create a new render target for it. We have a temp render target manager for this (which is why mem consumption is increased momentarily, but stabilized with time as the manager does garbage collection). These temp render target creation events ended up creating noise in the frame debugger event stream which manifested as flickering. Fix is incoming.

  3. Response avatar

    Resolution Note (fix version 2019.4):

    When the game view is resized we need to create a new render target for it. We have a temp render target manager for this (which is why mem consumption is increased momentarily, but stabilized with time as the manager does garbage collection). These temp render target creation events ended up creating noise in the frame debugger event stream which manifested as flickering. Fix is incoming.

  4. Response avatar

    Resolution Note (fix version 2018.4):

    When the game view is resized we need to create a new render target for it. We have a temp render target manager for this (which is why mem consumption is increased momentarily, but stabilized with time as the manager does garbage collection). These temp render target creation events ended up creating noise in the frame debugger event stream which manifested as flickering. Fix is incoming

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.