How to reproduce:
1. Open the attached “IN-109074“ project
2. Open the “SampleScene“
3. In the Hierarchy window, select “T → default“
4. In the Inspector window, go to the Line Renderer Component
5. Under the Materials Tab, assign the “Element 0“ value to “CrashMaterial“
6. Observe the crash

Reproducible with: 2022.3.6f1 (b9e6e7e9fa2d), 2022.3.9f1
Not reproducible with: 2022.3.5f1, 2022.3.64f1, 6000.0.54f1, 6000.1.14f1, 6000.2.0b11, 6000.3.0a3
Fixed in: 2022.3.10f1

Reproducible on: MacOS 15.5 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested

Notes:
- For consistent reproduction, the “IN-109074“ project should be unzipped each time when testing
- The issue doesn’t reproduce when the project is created with Universal Render Pipeline (URP)
- The crash happens when using the Line, Mesh, and Skinned Mesh Renderers

First few lines of the stack trace:

{noformat}0x00007ff68fb37933 (Unity) GfxDevice::ExecuteAsync
0x00007ff68fe257de (Unity) GfxDeviceClient::ExecuteAsync
0x00007ff68f6739b6 (Unity) ForwardShaderRenderLoop::StartRenderJobs
0x00007ff68f66ee7c (Unity) ForwardShaderRenderLoop::PerformRendering
0x00007ff68f66b017 (Unity) DoForwardShaderRenderLoop{noformat}