Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2018.1.X, 2018.2.X

Votes

0

Found in

2018.1.0f1

Issue ID

1025355

Regression

Yes

Crash when using the GPU profiler: TexturesD3D11Base::RemoveComputeBuffer

Graphics - General

-

Unity crashes when GPU profiler is active and rendering APIs are switched. It's more easily reproducible if a RenderTexture is used.

Repro steps:

- Use the RenderTexture scene from the SampleUI project: http://u3d.as/aiR
- Open the profiler window and select GPU profiling
- press play
- go to Settings->Player-> switch from Dx11 to Dx12
- Press play.

at this point, 90% of the time, I got crash 1:

0x0000000141F0B511 (Unity) TexturesD3D11Base::RemoveComputeBuffer
0x0000000141EECADD (Unity) BufferD3D11::CleanUp
0x0000000141EEC418 (Unity) BufferD3D11::`vector deleting destructor'
0x0000000141F378FD (Unity) GfxDeviceD3D12::DeleteBuffer
0x0000000141F6EF1E (Unity) GfxDeviceWorker::RunCommand
0x0000000141F715EB (Unity) GfxDeviceWorker::RunExt
0x0000000141F71718 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x0000000140A757F8 (Unity) Thread::RunThreadWrapper
0x00007FFD4CD01FE4 (KERNEL32) BaseThreadInitThunk
0x00007FFD4F47F061 (ntdll) RtlUserThreadStart

If you do not get Crash 1, try changing the rendering api a few times ( Vulkan and OGL Core also work for this purpose) and pressing play, and then close Unity.
100% of the time I get crash2:
0x0000000141F3FFA7 (Unity) GfxDeviceD3D12::QueueRelease
0x0000000141F359AD (Unity) BufferD3D12::CleanUpResource
0x0000000141F32648 (Unity) BufferD3D12::`vector deleting destructor'
0x0000000141EFBA8D (Unity) GfxDeviceD3D11Base::DeleteBuffer
0x0000000141F6EF1E (Unity) GfxDeviceWorker::RunCommand
0x0000000141F715EB (Unity) GfxDeviceWorker::RunExt
0x0000000141F71718 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x0000000140A757F8 (Unity) Thread::RunThreadWrapper
0x00007FFD4CD01FE4 (KERNEL32) BaseThreadInitThunk
0x00007FFD4F47F061 (ntdll) RtlUserThreadStart

Editor logs from Crash 1 and Crash 2 are attached to this case as txt files.

Cloud not reproduce in 2017.4.0f1

If Crash 2 is a separate case, it is also reported here: 1025406

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.