UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Go to DevTools>Network, open a WebSockets connection
2. Receive a large WebSockets message (mine is about 150 MB)
3. Try to scroll the 'frames', it does not scroll. Try to click the large message, nothing happens.

What is the expected behavior?
Large messages should not cause the WebSockets frames display to become unresponsive.

What went wrong?
My application sends the huge message early after page load, and then sends lots of small messages after that first initial load.

Scrolling through the small messages, I have no issue.

However, when I try to scroll up to the beginning where the large WebSockets message is, it freezes and takes several minutes before finishing the scroll so that the large message is visible. Once it becomes visible, the frames display is frozen and I can't click the frame to view the contents or scroll back down. It never becomes responsive again until I refresh the page.

Did this work before? No 

Chrome version: 66.0.3359.139  Channel: stable
OS Version: OS X 10.13.4
Flash Version: 

The exact length of the large frame shows as '153788738'