node.js - Why does nodemon/grunt auto reload causes continous heapdumps to be written to file?

Question

I'm using the heapdump module to investigate memory leaks in my node.js app. In development I'm using Grunt and nodemon to auto build (typescript => js) and reload the app. I've found that even including the heapdump module with var heapdump = require('heapdump'); causes heapdump files to continuously be written to the project root directory after I change a file. Here's an example of the filenames:

ls -1 heapdump-*
heapdump-16798025.709229.heapsnapshot
heapdump-16804706.868278.heapsnapshot
heapdump-16810376.817875.heapsnapshot
heapdump-16817216.844404.heapsnapshot
heapdump-16821854.974467.heapsnapshot
heapdump-16827753.236280.heapsnapshot
heapdump-16832525.325178.heapsnapshot
heapdump-16837019.589238.heapsnapshot
heapdump-16841498.201869.heapsnapshot

What's causing this and how can i prevent it from happening?

EDIT: I created a nodemon.json file with the following:

{
  "verbose": true,
  "ignore": ["./*.heapsnaphot", "data/*"]
}

But still doesn't stop the problem. The nodemon log looks like this:

[nodemon] files triggering change check: www.js
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] www.js

[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*
[nodemon] changes after filters (before/after): 1/0
[nodemon] files triggering change check: heapdump-15717150.745801.heapsnapshot
[nodemon] matched rule: **/*.*

As you can see the ignore rule isn't working on the heapdump files.

question from:https://stackoverflow.com/questions/65932557/why-does-nodemon-grunt-auto-reload-causes-continous-heapdumps-to-be-written-to-f

Answer 1

Waitting for answers