New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory exhaustion after some time #1953
Comments
This is extremely easy for me to reproduce in my codebase, since I have many separate However, running this as Note: The
Here's the full contents of Detailsmodule.exports = {
/**
* CUSTOMIZATIONS: Tweaks to the default config are below this line.
*/
"port": 3000,
"listen": "0.0.0.0",
"files": [
'css/**/**.css', // CSS
'templates/**/*.ss', // SilverStripe templates
// JS (reloads page)
'javascript/foot/**/*.js',
'javascript/custom-elements/**/*.js',
'javascript/head/**/*.js',
'javascript/build/*.js',
],
"watchEvents": [
"change"
],
"watch": true,
"notify": false,
/**
* DEFAULTS: Unchanged defaults are below this line.
*/
"ui": {
"port": 3001
},
"ignore": [],
"single": false,
"watchOptions": {
"ignoreInitial": true
},
"server": false,
"proxy": false,
"middleware": false,
"serveStatic": [],
"ghostMode": {
"clicks": true,
"scroll": true,
"location": true,
"forms": {
"submit": true,
"inputs": true,
"toggles": true
}
},
"logLevel": "info",
"logPrefix": "Browsersync",
"logConnections": false,
"logFileChanges": true,
"logSnippet": true,
"rewriteRules": [],
"open": "local",
"browser": "default",
"cors": false,
"xip": false,
"hostnameSuffix": false,
"reloadOnRestart": false,
"scrollProportionally": true,
"scrollThrottle": 0,
"scrollRestoreTechnique": "window.name",
"scrollElements": [],
"scrollElementMapping": [],
"reloadDelay": 0,
"reloadDebounce": 500,
"reloadThrottle": 0,
"plugins": [],
"injectChanges": true,
"startPath": null,
"minify": true,
"host": null,
"localOnly": false,
"codeSync": true,
"timestamps": true,
"clientEvents": [
"scroll",
"scroll:element",
"input:text",
"input:toggles",
"form:submit",
"form:reset",
"click"
],
"socket": {
"socketIoOptions": {
"log": false
},
"socketIoClientConfig": {
"reconnectionAttempts": 50
},
"path": "/browser-sync/socket.io",
"clientPath": "/browser-sync",
"namespace": "/browser-sync",
"clients": {
"heartbeatTimeout": 5000
}
},
"tagNames": {
"less": "link",
"scss": "link",
"css": "link",
"jpg": "img",
"jpeg": "img",
"png": "img",
"svg": "img",
"gif": "img",
"js": "script"
},
"injectNotification": false
}; |
p.s. Possibly related to #1083 |
Thanks @dsuarezv & @patricknelson - I'll look into this |
Just circling back to this issue, too. See if it stops crashing after you remove |
Issue details
Hi there,
I'm finding that browser-sync crashes because of memory exhaustion after a day or two running continuously. Here is the stack trace I get:
The machine is Linux 64bits running Ubuntu 21.
I don't know if it's related, but I'm including images and reloading if they change, maybe this is contributing to exhaust the memory more quickly. The images don't change very often, however.
I had core dumps disabled, I can enable them and send the dump if you need it.
Steps to reproduce/test case
See gulp script below. Just leave it running for a full day making changes here and there, it's crashed in the morning.
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
API
Gulp
CLI
Grunt
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
The text was updated successfully, but these errors were encountered: