UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.49 Safari/537.36

Steps to reproduce the problem:
1. Open the Developer Tools and go to the Network Tab BEFORE you go to a website that has websockets (i.e. http://www.websocket.org/echo.html)
2. Click on "Connect" on the site
3. Look for the 101 status and click on the "Name" of the resource
4. Click on the "Frames" tab
5. Click "Send" on the Site

3. 

What is the expected behavior?
I should see the frames coming in and going out of the browser

What went wrong?
The DevTools of Chrome jump off the 101 Resource to the next in the list and shows a different resource.

With heavy WS traffic there is no chance of using the WebSockets debugger :(

Did this work before? Yes Before Version 48 (I have using this for a long time - when I upgraded to 49 or 50 its broken)

Chrome version: 50.0.2661.49  Channel: beta
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

The only workaround is to "Filter" the resources by the name of the WebSockets resource. But that is not good if you want to debug the ws frames and see what else is going on between the brower and the server