Comments (9)
droidenator
commented on July 29, 2024
1
I'm seeing the same thing. Stats event fires without issue and even though my usage_trend is like..22 and memory usage has grown over 5+ GCs, the leak event is never fired.
from node-memwatch.
marcominetti
commented on July 29, 2024
@xosuperpig can you provide an example to generate a leak?
from node-memwatch.
buptwinux
commented on July 29, 2024
I have also run all of example, but the "leak" event could not triggered...
just like this:
var hd;
memwatch.on('leak', function(info) {
console.log("leak:\n");
console.error(info);
if (!hd) {
hd = new memwatch.HeapDiff();
} else {
var diff = hd.end();
console.error(util.inspect(diff, true, null));
hd = null;
}
console.error('memory leak detected: ', info);
});
thank you very mach!
from node-memwatch.
buptwinux
commented on July 29, 2024
@droidenator , did your problem keep on？how solve it？
from node-memwatch.
zombieyang
commented on July 29, 2024
(function() {
var i = 0;
function run() {
return new Promise(function(resolve) {
if (i % 10000 === 0) console.log(process.memoryUsage());
i++;
setTimeout(function() {
if(i === 10000 * 10) return resolve();
resolve(run());
}, 0);
}).then(function() {});
}
run();
})();
this is a Promise leak example in node 4.2 lts
@marcominetti
from node-memwatch.
joeytwiddle
commented on July 29, 2024
I'm running node on a Mac Book Pro. I notice that garbage collection is sometimes running in pairs quite close together, and the second one reclaims a little bit of memory that the first did not.
As a result, my process never fulfils the "5 increases in a row" condition, despite the overall memory usage increasing!
Example log:
[log] (modules/debugTools.js:105:29) naive: 111356664
[log] (modules/debugTools.js:105:29) naive: 165723376
[log] (modules/debugTools.js:112:29) postgc: 210520304 <--
[log] (modules/debugTools.js:105:29) naive: 217459856
[log] (modules/debugTools.js:105:29) naive: 246305776
[log] (modules/debugTools.js:112:29) postgc: 261949272 <-- increase
[log] (modules/debugTools.js:105:29) naive: 286845272
[log] (modules/debugTools.js:105:29) naive: 322883080
[log] (modules/debugTools.js:105:29) naive: 394269064
[log] (modules/debugTools.js:105:29) naive: 430305896
[log] (modules/debugTools.js:105:29) naive: 466342728
[log] (modules/debugTools.js:105:29) naive: 555195016
[log] (modules/debugTools.js:105:29) naive: 591238152
[log] (modules/debugTools.js:105:29) naive: 621307808
[log] (modules/debugTools.js:105:29) naive: 657373616
[log] (modules/debugTools.js:105:29) naive: 772633808
[log] (modules/debugTools.js:112:29) postgc: 765572840 <-- increase
[log] (modules/debugTools.js:105:29) naive: 801502320
[log] (modules/debugTools.js:105:29) naive: 837576568
[log] (modules/debugTools.js:112:29) postgc: 752163536 <-- decrease
[log] (modules/debugTools.js:105:29) naive: 778027472
[log] (modules/debugTools.js:105:29) naive: 814065312
[log] (modules/debugTools.js:105:29) naive: 850105616
[log] (modules/debugTools.js:105:29) naive: 886142184
[log] (modules/debugTools.js:105:29) naive: 1033814136
[log] (modules/debugTools.js:105:29) naive: 1062652456
[log] (modules/debugTools.js:105:29) naive: 1100131120
[log] (modules/debugTools.js:105:29) naive: 1136174304
[log] (modules/debugTools.js:105:29) naive: 1172210776
[log] (modules/debugTools.js:105:29) naive: 1208247248
[log] (modules/debugTools.js:105:29) naive: 1237084008
[log] (modules/debugTools.js:105:29) naive: 1273126792
[log] (modules/debugTools.js:105:29) naive: 1301980896
[log] (modules/debugTools.js:105:29) naive: 1338017520
[log] (modules/debugTools.js:105:29) naive: 1374053992
[log] (modules/debugTools.js:105:29) naive: 1433063768
[log] (modules/debugTools.js:112:29) postgc: 1563459896 <-- increase
[log] (modules/debugTools.js:112:29) postgc: 1430329544 <-- decrease
[log] (modules/debugTools.js:105:29) naive: 1462015280
[log] (modules/debugTools.js:112:29) postgc: 1343619976 <--
[log] (modules/debugTools.js:112:29) postgc: 1343478256 <-- decrease
[log] (modules/debugTools.js:105:29) naive: 1354060952
[log] (modules/debugTools.js:105:29) naive: 1390162888
[log] (modules/debugTools.js:105:29) naive: 1426208992
[log] (modules/debugTools.js:105:29) naive: 1455071568
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
<--- Last few GCs --->
204211 ms: Scavenge 1398.3 (1454.9) -> 1398.3 (1454.9) MB, 0.5 / 0 ms (+ 2.1 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
206404 ms: Mark-sweep 1398.3 (1454.9) -> 1396.5 (1454.9) MB, 2192.8 / 0 ms (+ 3.2 ms in 2 steps since start of marking, biggest step 2.1 ms) [last resort gc].
208034 ms: Mark-sweep 1396.5 (1454.9) -> 1396.5 (1454.9) MB, 1630.2 / 0 ms [last resort gc].
The leak is detected fine when I use slightly_leaky.js with i < 100000. But the above is when I drop the same setInterval() into my app. (The app is supposed to be idle!) So I guess it's something else going on in my app that throws off the detection.
I wonder if we could use a different condition for detection. Perhaps something like "over threshold T after 5 consecutive GCs" where T can be set manually, or perhaps chosen as "10 x the memory usage one minute after startup".
Notably the problematic gc pairs do not occur when I reduce the speed at which the leak grows, so perhaps I am just being too aggressive/impatient with my tests.
from node-memwatch.
joeytwiddle
commented on July 29, 2024
In the meantime, you can fake a 'leak' event like this...
memwatch.on('stats', function(d) {
// If the app is using more than 3GB RAM
if (d.current_base > 3000000000) {
// Either call your leak handling function directly:
// ...
// or manually trigger a 'leak' event, for what it's worth:
memwatch.emit('leak', { growth: d.current_base, reason: 'app using too much RAM lol' });
}
});
from node-memwatch.
marcominetti
commented on July 29, 2024
hi @joeytwiddle, i'll delve into this on monday... ;)
from node-memwatch.
egistli
commented on July 29, 2024
@xosuperpig I modified the leaking http server in the example a bit and ran the http server for a while then memwatch did emit several leak events.
What I modified is to reduce the interval of leaking from 1000 to 10.
from node-memwatch.
Related Issues (20)
- discrepancy between 'pm2 monitor', 'top', and memwatch HOT 1
- can't install on node 8.x HOT 3
- Rename this repository to `memwatch-next`?
- Heap usage: `int` and `time_t` are used instead of `size_t` by mistake HOT 1
- No dump generated on Node 6.9.1 + BeanStalk
- Create Pre-builds
- Cannot install in Node 8.9.4
- Cannot install on node 10.0.0 HOT 6
- cannot install memwatch-next for node v8.x HOT 3
- Error installing it in the Docker alipine node 8.11.4 image HOT 3
- For those needing node 9.x+ support HOT 1
- Install failure on osx Mojave HOT 2
- cannot install on node v11.8.0 HOT 13
- spurious message on start
- Cannot install on node version 12.13.1 HOT 5
- Can't install on Node v13.6.0 with npm 6.13.4, 'Handle': is not member of 'v8' HOT 1
- Memory leaks issue
- Please mark as deprecated HOT 4
- cannot install on MacOS HOT 1
- not able to install
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-memwatch.