Alright. Things goes well with my bandwidth-hero-proxy fork.
At first, I thought that the memory is never cleaned, But turns out sometime it is cleaned and then RAM usage drops to 9%.
And that was interesting way of NodeJS / V8 handle memory.
When idle after usage, Memory usage was 22%.
Well. I guess i could sleep for this one
At first, I thought that the memory is never cleaned, But turns out sometime it is cleaned and then RAM usage drops to 9%.
And that was interesting way of NodeJS / V8 handle memory.
When idle after usage, Memory usage was 22%.
Well. I guess i could sleep for this one
Well. For ytmous,
In nightly branch, The memory leak problem is ultimately decreased.
But i think i know what was causing it to happen.
In nightly branch, The memory leak problem is ultimately decreased.
But i think i know what was causing it to happen.
Yonle: Notes and Other
Well. For ytmous, In nightly branch, The memory leak problem is ultimately decreased. But i think i know what was causing it to happen.
You see those two codes that i marked?
Yeah. Seems like the event functions is recreated in the memory, too.
Yeah. Seems like the event functions is recreated in the memory, too.
I know how to fix it.
Just like how i did with bandwidth-hero-proxy, Separating the event functions.
However, For code like ytmous, It is not always an easy task to rewrite those big codes up.
Just like how i did with bandwidth-hero-proxy, Separating the event functions.
However, For code like ytmous, It is not always an easy task to rewrite those big codes up.
Not only that i need to separate those functions,
I also need to use my IQ to know what to put with those shortened function.
I also need to use my IQ to know what to put with those shortened function.