memory leak about flood HOT 13 CLOSED

does this happened if you are not using developing startup?
for example: npm run build and node dist/index.js.
There maybe some incompatible between apple silicon and tsx(esbuild)

Running npm run build and node dist/index.js works without any problems.

Then I think this is caused by tsx/esbuild... and I have no clue about how to fix it 😥

please just use production build.

from flood.

very likely this is caused by rtorrent request queue. there maybe a bug. I replace it with p-queue, and everythink looks fine.

from flood.

I'm on master and have memory leak problems. When running the flood development server, it quickly starts consuming upwards of 16 GB of memory. After some time, it either crashes or my Mac prompts me to close other applications, as I'm out of memory.
This is the graph after closing flood (node):

from flood.

I'm on master and have memory leak problems. When running the flood development server, it quickly starts consuming upwards of 16 GB of memory. After some time, it either crashes or my Mac prompts me to close other applications, as I'm out of memory. This is the graph after closing flood (node):

what bt client are you using?

from flood.

@trim21 I'm running rtorrent using the following command:

docker run -it --rm -v ./volumes/config:/config -v ./volumes/data:/Users/ffactory/data --user 1000:1001 -p 0.0.0.0:6881:5000 -e HOME=/config jesec/rtorrent

edit:
Node v20.0.0
npm 9.8.1

from flood.

@trim21 I'm running rtorrent using the following command:

docker run -it --rm -v ./volumes/config:/config -v ./volumes/data:/Users/ffactory/data --user 1000:1001 -p 0.0.0.0:6881:5000 -e HOME=/config jesec/rtorrent

edit: Node v20.0.0 npm 9.8.1

looks like there are more than one memory leak bug...

from flood.

it quickly starts consuming upwards of 16 GB of memory

how many torrents do you have in rtorrent?

and "it quickly starts consuming upwards of 16 GB of memory", how quickly?

from flood.

@trim21 the number of threads keeps rising (currently 2.9k)

Within 5 seconds of starting the server, it's already at 4 GB, after total 30 seconds it's at 9 GB and the number of threads approaches 1k.

After killing both npm run start:development:server and npm run start:development:client it takes more than 20 seconds for the node process to fully close. Used memory and number of threads quickly decline during that time.

Edit: I should note, I'm using a MacBook Pro with Apple silicon. On my VPS (Ubuntu 20, x86) I'm using flood with zero problems.

from flood.

@trim21 the number of threads keeps rising (currently 2.9k)

Within 5 seconds of starting the server, it's already at 4 GB, after total 30 seconds it's at 9 GB and the number of threads approaches 1k.

After killing both npm run start:development:server and npm run start:development:client it takes more than 20 seconds for the node process to fully close. Used memory and number of threads quickly decline during that time.

Edit: I should note, I'm using a MacBook Pro with Apple silicon. On my VPS (Ubuntu 20, x86) I'm using flood with zero problems.

I don't have Apple silicon, I can't help with this...

from flood.

@trim21
I don't have Apple silicon, I can't help with this...

I'm happy to help investigate this if you have any clues. 🙂

from flood.

@trim21 the number of threads keeps rising (currently 2.9k)

Within 5 seconds of starting the server, it's already at 4 GB, after total 30 seconds it's at 9 GB and the number of threads approaches 1k.

After killing both npm run start:development:server and npm run start:development:client it takes more than 20 seconds for the node process to fully close. Used memory and number of threads quickly decline during that time.

Edit: I should note, I'm using a MacBook Pro with Apple silicon. On my VPS (Ubuntu 20, x86) I'm using flood with zero problems.

does this happened if you are not using developing startup?

for example: npm run build and node dist/index.js.

There maybe some incompatible between apple silicon and tsx(esbuild)

from flood.

does this happened if you are not using developing startup?

for example: npm run build and node dist/index.js.

There maybe some incompatible between apple silicon and tsx(esbuild)

Running npm run build and node dist/index.js works without any problems.

from flood.

@trim21 okay, I'll do that. Thanks for your efforts.

from flood.