This issue has been plaguing me for about a week now. On the latest Chrome version, I'm unable to open a WebSocket request via DevTools to see individual frames. This is happening on all websites.
I have no filter added anywhere I can see, so the invalid regex issue that I'm seeing in the Devtools' devtools window is a mystery.
I'm on Chrome Version 106.0.5249.103 (Official Build) (arm64), on OSX, and haven't seen this problem before.
Related
I found there is no hex viewer in my Chrome's WebSocket dev tools, as in picture 2, unlike picture 1 on my colleague's computer.
I didn't find corresponding view settings. I tried to reboot my computer and reinstall Chrome, even the beta version, still not work.
Thanks to someone who would help me out!
OS version: macOS Catalina 10.15.7, Chrome version: 87.0.4280.88
picture1 normal view
picture2 no encoding settings
This appears to be a bug in Chrome 87. I suspect that your colleague is using a different Chrome version.
See https://bugs.chromium.org/p/chromium/issues/detail?id=1151164#c7, which claims that the bug was fixed in Chrome 89.0.4348.0. The solution appears to be one of:
Switch to the Chrome Beta channel
Use a debug extension for Chrome such as WebSocket Frame Inspector as suggested here.
See also these related SO questions:
How can I change the binary message display format in the Chrome/Edge debugger?
Chrome DevTools. The encoding switch bar of the websocket frame viewer disappeared
I have some weird thing going on in my machine. When loading a specific website at work and opening the Chrome devtools, the website's tab gets frozen, Chrome task manager shows > 100% CPU usage and all is frozen and unusable.
I’ve tried the following, none worked:
Disabled all extensions
Cleared cookies
Restarted Chrome
When loading the same URL with devtools in Incognito mode, all is splendidly working and smooth as butter.
What can be the problem here? I'm using Chrome version 79.0.3945.130, which is currently the latest
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
When I start Postman I see the icon appear in the Dock and in the Force Quit window, and I can click on the icon in the dock and Postman appears in the menu bar, with the single option "Quit Postman." So it's running, but the window doesn't appear. This morning I upgraded Chrome to 55.0.2883.95, Chromium to 58.0.2991.0, and Chrome Canary is at 58.0.2990.0.
Is there a way to switch Postman from Chrome to Chromium or Chrome Canary (i.e., to test Postman with different builds)? Or to revert Chrome to any older build? Or any other ideas to get Postman working?
The chrome addon for Postman will be depricated soon.
There are now fully functional standalone apps for Windows/Mac/Linux here. They work just as well as the Chrome addon and even have some additional features. I would suggest moving to the standalone apps.
In Chrome I googled "Postman," which took me to the Chrome App store, and the Postman page has a green button for "Launch App Now." That worked!
try disable and then enable the extension.
It worked for me.
Sometimes google chrome doesn't load it properly.
I had a nearly similar problem, where Chrome postman app (extension) fails to post/get/etc. It was unable to access the internet for some reason. After trying many solutions, it seems that the javascript setting in Chrome was causing it. You need to enable javascript in Chrome, restart Chrome, then the postman app will work.
Hi I was using selenium chrome drivers as interactive service to open some websites. It was working fine. Suddenly found that the session is not loading correctly and showing black page. Found following error:
chrome automation extension has crashed. click this balloon to reload the extension
Found that with chrome browser version was updated to v51 and selenium-chromedriver 2.21 is compatible with v50.
Downgraded chrome browser to v50. Now it is working fine.