Force a Crash! With DATA FLOW DISCONTINUANCE

Type to force data packet assignment and flow activity complexity to above average. As the countdown to champ select hits 0, change masteries and runes, starting with masteries first. The clock disappears after 0 but the client will stall closing to send the information it needs to get out from your pc. Someone in that game is going to have the wrong information uploaded, and will force them to DC. It might even be you. I call it DDC (Data-discontinuance). The packet is lost and is never received by a client that thinks it already has the proper packets. This causes a discrepancy for them as they data flow will be incomplete and will not load, thereby being forced to reload the entire thing from the very first data packet.

Can anyone confirm this from 1st-hand experience?