socket.io-client:socket keeps on showing in my browser console - javascript

I tried to use DEBUG = * for debugging purposes in javascript socket.io. After debugging, I erased my codes related to that because I don't need it anymore at the moment. But when I try to run my application again, the debugger is still printed in my browser console.
I need help, please. I just want it gone so that I can view my other consoles. What happens when I console something, my browser console gets flooded with socket.io-client:socket and i can't read my console anymore.

Related

The console in dev tools is blank

I've been attempting to verify some information but I haven't been able to receive any data on the console. I suspect that my code may not be functioning properly, so I accessed just github.com/reddit.com, and here the console produced an error. Initially, I believed that this issue may be related to a problematic browser extension, so I disabled all extensions and opened an incognito window. However, in this case, the console is entirely empty. Does anyone have any suggestions as to what could be the issue?Below are the screenshots:
Tried running a js web app and found the console showing error. Then diabled the extensions and found the console completely blank.

While running VS Code Live Server (Go Live), the browser is crashing. I am using Google Chrome as default

While running VS Code Live Server (Go Live), the browser is crashing with the below mentioned error. I am using Google Chrome as default. I re-installed VS Code after uninstalling completely (from cache even), restarted browser, and then restarted PC as well with no use. When I checked "Use Local Ip" in LiveServer>Settings:, server is taking too long to respond and eventually fails to load the page (Error: "This site can't be reached"). Another important thing is that Chrome is opening every other website properly. This problem exists only when opening VS Code Live Server. Below is the error code:
Chrome Browser Error:
"Aw, Snap!
Something went wrong while displaying this webpage.
Error code: STATUS_BREAKPOINT"
Another popup is also showing up simultaneously:
"DevTools was disconnected from the page.
Once page is reloaded, DevTools will automatically reconnect."
(This didn't seem like a bug in the code of script.js)
Found the Solution:
Indeed it is a bug in the code of script.js.
If you are having exactly the same problem as I described, let us first see what we don't need to do, as I found these suggestions everywhere, and none will work when both VS Code and your browser are perfectly fine (they only appear to be not working):
No need to restart or reinstall VS Code.
No need to restart or reinstall browser.
No need to restart the PC
No need to disable browser extensions or VS Code extensions.
No need to change LiveServer Custom Browser; you can keep it
default.
No need to change LiveServer>Settings>Use local ip or Use browser
preview (you can keep them both unchecked if they are already
unchecked by default)
However, if you use firefox, console shows the error: "Uncaught out of memory"
Here, I got the first hint. Firefox at least told me to look at memory, but it is not about the memory we think. It is not about multiple tabs opened, lack of disk space, unstable disk, etc. It is the accidentally generated infinite loop in the code which is causing the memory problem (check your code carefully to find it).
In my case, I accidentally didn't tell it to execute the next iteration (i.e., missing counter update, increment, i++) and it is stuck in the same while loop forever, as the condition is satisfied forever without any counter update.
After fixing the code, the below error might show up in the console. Just refresh the page and it will go away.
"favicon.ico:1 Failed to load resource: the server responded with a status of 404 (Not Found)"
Note: Unless you fix the code or comment it out, other linked files (like .html) in the folder wouldn't work either.

Express server console problems

I'm setting up an Express Server and it's working properly or seems to be. What I send gets rendered in the browser and my console.log test statements show up in my terminal but when I inspect the browser page it is not showing up in the browser console. I've never had this happen before. Any input??
You cannot show express console logs on browsers console.

Typing on a Browser console

This might sound trivial but I need to to add some lines to the Chrome's Javascript browser console on Ubuntu. I've opened the browser console by pressing Ctrl+Shift+J and when I try to type in, nothing happens(the console's not editable). Are there any steps that am missing here?
Browser Console
Try Ctrl+Shift+K for web console to execute Javascript expressions

How to remove all recent console commands from Google Chrome

Google Chrome v48.0.2564.116 (64-bit) for Mac OS seems to retain all console commands indefinitely. None of the following have any affect:
clear()
console.clear()
Command-K
turning off "preserve log" and "show all messages"
Clear browsing data, from the beginning of time, all options check marked - removing all cookies
quitting and restarting or shutting down and rebooting.
Any combo of the above.
Unable to locate a chrome_debug.log file anywhere on the system (i.e. logging is not check marked).
Trashing Google Chrome and the associated library files then re-installing got rid of the console history, but the new version nonetheless holds all console subsequent console entries indefinitely.
Any insights? Any idea where this information gets stored?
If you are using windows 10. Just Simply go the console and right click then click on clear console
Thanks to Karmiphuc and the following link:
How to remove all recent console command
which mostly answers the question.
It's slightly understated there that, on Mac OS at least, you have to call the developer tools twice consecutively.
So 1st pull up a browser window, and do Command-Shift-I (Mac shortcut).
Then, making sure the Developer Tools window is undocked, do a second Command-Shift-I which pulls up yet another Developer Tools window.
Now look under Local Storage > chrome-devtools://devtools > consoleHistory.

Categories