Ok, this is very odd. I wasn't getting this bug whatsoever because I don't have tracers "turned off". When I changed my viewmodel_fov to 360 it took about 5 clips of a scattergun to get the bug and for CUtlLinkedList overflow! (exhausted index range) to appear in the console. This could make sense because the game is essentially trying to draw the tracers off screen, which I wouldn't be surprised could cause it to just be unable to do so and for the list to exceed its defined range.
However... when I set my viewmodel_fov to 0.001 it takes me at least 20 clips to trigger the bug and most notably the error message does NOT appear in the console. Whether or not this is an error in writing to the console, I don't know. I would understand if it just took longer(after all, 0.001 is still on screen, though some of the tracers are bending at such an angle that they would be fully outside your FOV), but the lack of error message is making me scratch my head.
EDIT: It's just an error in writing to the console. Sometimes I get the error message, sometimes I don't. It's not uncommon for that to happen in Source console, so I'd just assume that it should be there every time, but it just isn't very reliable.
In conclusion, it seems that extreme viewmodel FOVs are the culprit. Could everyone who is getting this bug please confirm that they have an extreme viewmodel_fov in their configs so we aren't wasting our time? Thank you in advance.