Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.0a6
Issue ID
1017013
Regression
No
DrawBuffers() error or FillQuadIndexBuffer crash when clicking and dragging pointer while particle system is being simulated
To reproduce:
1. Open any project and create a particle system
2. In Scene view, click on particle system and press Simulate
3. While still in Scene view, click and drag the pointer
Expected: no errors appear
Actual: console outputs errors regarding DrawBuffers() or crashes (two releases only), check .giff attached
Reproduced in: 2017.2.2p2, 2017.3.1p4, 2018.1.0b12, 2018.2.0a6
Note1: error is printed out when changing selection rectangle's size by dragging mouse. Full error: "DrawBuffers() got a range of indices but no index buffer"
Note2: crashes on two releases 2017.2.2p1 and 2017.2.2p2 (just released) with stack trace:
0x00000001404C8B89 (Unity) DynamicVBO::FillQuadIndexBuffer
0x00000001404CB977 (Unity) DynamicVBO::ReleaseChunk
0x0000000141D2365C (Unity) GfxDeviceWorker::RunCommand
0x0000000141D2537B (Unity) GfxDeviceWorker::RunExt
0x0000000141D04612 (Unity) GfxDeviceWorker::Run
0x0000000141D117A9 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00000001407B9AA8 (Unity) Thread::RunThreadWrapper
0x00007FFA38491FE4 (KERNEL32) BaseThreadInitThunk
0x00007FFA39B3EFC1 (ntdll) RtlUserThreadStart
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
DerDicke
Nov 05, 2020 14:38
Man... just ignore my previous comments altogether. I was just using UnityEditor.Handles.DrawLines() wrong.
DerDicke
Nov 05, 2020 12:26
Confirmed for Unity 2019.3.11f1 (64-bit).
DerDicke
Nov 05, 2020 11:39
Confirmed for Unity 2018.2.18f1 (64-bit) when using UnityEditor.Handles.DrawLines() for some Artwork that works and displays perfectly in any other case.
Confirmed for Unity 2018.3.10f1 (64-bit). Crashes Unity Editor in 2018.3.