I'm Having some Really Strange Bug Problems with the New Queue [Client]

I've been having huge problems with the new Dynamic Queue that keeps making me doge unintentionally.

Im not talking about when you forget to lock in or ban and it kicks you out, although that is a little annoying. Im talking about a minor bug that can make you dodge if you don't know what to do to fix it and one major bug that, when it happens will make you dodge with nothing you can do about it.

These seem like lag when first explained, they very well could be, but my connection on everything else works perfectly fine and I've had a few friends saying they've had similar problems. However, I haven't seen anyone other than my friends talking about bugs like this so I had to ask because they're getting REALLY frustrating.

Bug 1# Occasionally, when you get to the champion locking in segment of the queue, if you have selected your champion that you wish to play before hand in the champion declaration, pushing the lock button will make the button noise, show the animation, but the button will do nothing and reappear, asking you to lock in again. It will do this indefinitely until you dodge if you don't know what to do. It seems however that you have to click on the champion or another to make the button work. I might think this isn't a bug, just an odd function, but the button would be grayed out or something of the sort if Riot wanted you to click on a champion before locking in, even if you picked one. Problem is very annoying and has caused me to dodge several queues until I figured out how to avoid this.

Bug 2# This bug is INCREDIBLY frustrating and has cost me at least 2 hours of dodge penalty time. It seems like lag, and it might be just that (why I'm asking around) but it doesn't seem to be, as every other thing involving my own connection is still working fine when this bug happens. This occurs randomly during the banning and locking in phase where the client seems to not register anything the current banner is doing. The slot that displays the champion they're going to ban remains empty and the clock runs down until it reaches zero. The slot will remain empty and the clock will stay at zero even though the client recognizes the next person in line as currently "banning". This only happens once during the queue as far as I can remember but the client doesn't update for a good 30 seconds or so. Meaning that, if the person that the client locks up on is the one in front of me, I am almost certain to dodge because I am unable to ban a champion even though the clock is ticking down. This bug occurs VERY often.

I really could use some help. I feel like I'm just going to get people telling me it's lag but I'm at my wits end. My internet seems to be working fine with league and once I'm past the queue I don't really have any more lag problems. I may have missed some announcement on it if this is a problem Riot's recognized or something of the sort but I really don't know so I'm asking here to see if anyone can point out anything I should know but don't or if this is some sort of odd problem other people are having. I'm not sure but any help you have to give would really be appreciated.

Thanks.