ArtemGovorov
commented
1 year ago Thanks for reporting the issue.
When it happens, does browser page refresh (or Chrome restart) help?
Closed SuarezLuis closed 1 year ago
ArtemGovorov
commented
1 year ago Thanks for reporting the issue.
When it happens, does browser page refresh (or Chrome restart) help?
sawyerclick
commented
1 year ago I frequently run into this issue on various M1 Macs. Today, I received this error while attempting to git push for the first time. My entire computer froze, lost internet connection, and had to totally restart. I've narrowed it down to this extension as the culprit by disabling each I have installed one-by-one.
Will have to uninstall until this is addressed
ArtemGovorov
commented
1 year ago We are investigating the issue, and while we haven't been able to locally reproduced it, we have a few ideas to try and address it. We'll be releasing a new version with the fix attempt early next week.
The issue seems to be related to the volume of websocket writes on M1. Console Ninja only creates few websocket connections, but may send a lot of data over it over time (depending on how much console.log is used and logs in user code).
The M1 issue seems to be affecting other tools as well, even more severely it seems: https://github.com/lensapp/lens/issues/6063.
@suarezluis @sawyerclick, and everyone else watching/encountering the issue, to help us address it faster, can you please share some details about your use of the extension?
console.log calls in your code? If so, how much data was logged - just few objects/strings, or a lot of data was logged?ArtemGovorov
commented
1 year ago We have released some changes that may fix the issue in v0.0.87+.
@suarezluis @sawyerclick Can you please try the latest version and let us know if the issue is fixed for you? If the issue is still there, please share some more details:
SuarezLuis
commented
1 year ago @ArtemGovorov Thanks for the update, will try it with the new version and get back to you
eric-helix-93
commented
1 year ago I'm still getting the issue on version v0.0.87.
did you just have it installed and didn't use much, or you had it running for your projects and had a few console.log calls in your code? If so, how much data was logged - just few objects/strings, or a lot of data was logged?
I just installed this yesterday and only used it for about 2 hours. It was only logging strings and errors.
do you have autosave setting on in your VS Code for your file changes, or manually saving files when required?
No autosave, manually save the files
do you usually have 1-3 VS Code projects you're working with, or you typically have 5+ opened projects (with Console Ninja running) and multiple browser pages (with hot reload from your build tool) opened at the same time?
Only had the one VS code project open and running at the time and only one tab with the project running.
do you have any active VPN client or virus scanner (or any other tool that may be affecting/monitoring your network in any way)?
No active VPN client or virus scanner
smcenlly
commented
1 year ago Some additional questions for you @eric-helix-93 - can you tell us a little about your project type and logging behavior?
create-react-app? vite? vite with react? etc?Also wanted to check that you're using Mac M1?
eric-helix-93
commented
1 year ago @smcenlly
What project type were you using? E.g. create-react-app? vite? vite with react? etc?
It's a vite with react app.
Were you logging lots of values or only a small amount? I'd imagine the strings were fairly small? Did you get a lot of errors?
They were fairly small strings but I was getting a lot of errors as I was testing some API changes. We are using react query and a few of the logs and errors were triggering from the responses received from the API.
I am using an M1 Mac :)
SuarezLuis
commented
1 year ago Same here, issue persists, running single project on VsCode, create react app, M1 Ultra processor.
ArtemGovorov
commented
1 year ago @suarezluis Were you logging lots of values or only a small amount? Did you get a lot of errors logged?
dilincoln
commented
1 year ago Same here, macOS Ventura
creativeindustriesgroup
commented
1 year ago Same issue here - Pre-M1 Chip.
Device & OS: MacBook Pro 2019 15" 2.4 GHz 8-Core Intel Core i9 Radeon Pro Vega 20 4 GB Intel UHD Graphics 630 1536 MB 32 GB 2400 MHz DDR4 13.2.1 (22D68) (Also tested before the most recent update with the same issue) Running 3x Displays
Environment: Visual Studio Code: Version: 1.76.2 (Universal) Date: 2023-03-14T17:54:09.061Z (1 wk ago) Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin x64 22.3.0 Auto Save Enabled
VSC Extensions: GitLens Import cost PHP Server Prettier Simple React Snippets VS Code Counter Console Ninja v0.0.91
I seem to be able to run with no issues for around 2 hours and then will get the NO_BUFFER_SPACE error affecting all internet connection on the device. Shortly after, my Mac also Kernel Panics. I have deactivated Console Ninja and will report back if I can confirm that this is the source of my Kernel Panic/NO_BUFFER_SPACE error.
I have no VPN but do run Malwarebytes in the background. Browser Refresh, Restart does not work. Restarting react-scripts start does not work.
I access the site via http://localhost:3000 rather than via the LAN IP.
Hope this helps.
smcenlly
commented
1 year ago Can you please:
Diagnostics reports and Crash Reports (instructions here)smcenlly
commented
1 year ago @eric-helix-93, @creativeindustriesgroup, @suarezluis - can you please provide us with your MacOS Diagnostics reports and Crash Reports ([instructions here] so we can investigate further?
creativeindustriesgroup
commented
1 year ago @eric-helix-93, @creativeindustriesgroup, @suarezluis - can you please provide us with your MacOS
Diagnostics reportsandCrash Reports([instructions here] so we can investigate further?
Unfortunately I can't narrow down a specific time that the last panic happened. As soon as it happens again I'll get the time and send the logs over, unfortunately as I don't have a specific way of re-creating its a bit of a waiting game.
Some more environment factors which may or may not help: From package.json
"private": true,
"dependencies": {
"@airbrake/browser": "^2.1.8",
"@fortawesome/fontawesome-svg-core": "^6.2.1",
"@fortawesome/free-brands-svg-icons": "^6.2.1",
"@fortawesome/free-solid-svg-icons": "^6.2.1",
"@fortawesome/react-fontawesome": "^0.2.0",
"@stripe/react-stripe-js": "^1.16.4",
"@stripe/stripe-js": "^1.46.0",
"@testing-library/jest-dom": "^5.16.5",
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^13.5.0",
"bulma": "^0.9.4",
"clsx": "^1.2.1",
"crisp-sdk-web": "^1.0.12",
"date-fns": "^2.29.3",
"dotenv": "^16.0.3",
"firebase": "^9.15.0",
"logrocket": "^3.0.1",
"react": "^18.2.0",
"react-bulma-components": "^4.1.0",
"react-content-loader": "^6.2.0",
"react-dom": "^18.2.0",
"react-router-dom": "^6.6.2",
"react-toastify": "^9.1.1",
"sass": "^1.57.1",
"web-vitals": "^2.1.4"
},
"devDependencies": {
"react-scripts": "5.0.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}Some logs which I cannot confirm are from the correct crash/kernel panic but are around a similar time relate to the remoted process timing out/not responding, Adobe Creative Cloud CCXProcess and the watchman process. Again this is only suggestive for now until I can accurately pick out a crash report and even though Adobe CC is listed the crashing/network issues did go away when I uninstalled Console Ninja.
smcenlly
commented
1 year ago Yesterday we were able to reproduce the issue for ourselves. We were able to recover from the problem by killing all the associated console ninja processes:
ps -A | grep wallabyjs.console-ninja- | awk '{print $1}' | xargs killPlease note we are working on this issue as a high priority.
smcenlly
commented
1 year ago Today we identified and fixed the problem that was causing this issue.
The problem was actually a bug/behavior in one of our dependencies, node-fetch and they way that we were using it. To optimize performance, we were returning content immediately without processing the response body in some cases (the requirement to process the body is not explicitly mentioned in their docs). This is a known bug that can lead to sockets/file descriptors being left open and is apparently an issue on MacOS and Linux (see https://github.com/node-fetch/node-fetch/issues/1673).
The issue would exhibit when multiple errors occurred when running in a browser environment when we were using node-fetch to retrieve source maps for error processing
The problem is fixed in Console Ninja v1.0.105.
⚠️ IMPORTANT
If you have this problem, please update to Console Ninja
v1.0.105+.What happened?
While using Console Ninja in a create-react-app eventually the browser errors with ERR_NO_BUFFER_SPACE
Removing the extension and restarting the IDE fixes the problem
Version
v0.0.85
Steps to reproduce (or sample repo)
The issue can't be reproduced constantly
By looking online seems to be affecting only apple sillycon devices
Log output