http memory leak

[LongWuAha]

http.js :Provides http client requests to remote server and request-response objects for (Fast)CGI calls. will cause the memory to continuously increase,Is it a memory leak? This is the test code:

var http=require("http");
while (true) {
    var req=new http.ClientRequest("https://www.google.com/");
    var resp=req.send(true);
    resp.data.toString("utf-8");
}

[vahvarh]

Hi! I have added a bit of logging and garbage collector calls, but still seems to be an issue. Sent to developer team.

var http=require("http");
var i=0;
while (true) {
    var req=new http.ClientRequest("https://www.google.com/");
    var resp=req.send(true);
    resp.data.toString("utf-8");
    i++;
    if (i%10) system.gc(400);
    if (i%100==0) system.stdout.writeLine(i+" iterations");
}

[vahvarh]

Yes. We already had found it but this is not the only case. Searching deeper, will publish update within couple of days.

Sincerely yours, Vladimir Olenin, CEO

UAE: +971 50 561 2296
RUS: +7 903 671 0081
Skype: vahvarh
Telegram: @vahvarh

PRONETCOM FZ-LLC

UAE, Dubai, Dubai Internet City, bld 14, office 206
Russia, Moscow, Aleksandra Solzhenitsyna street, bld 23A

On 26 Jan 2024, at 04:53, AHA @.***> wrote:

Hi, It could be the socket.cc function JS_METHOD(_receive_strict) experienced a memory leak

— Reply to this email directly, view it on GitHub https://github.com/pronetcom/teajs/issues/31#issuecomment-1911238795, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJCEPQZBYG4JSHIKONMPW3YQL5AHAVCNFSM6AAAAABCDWMEHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRGIZTQNZZGU. You are receiving this because you commented.

[LongWuAha]

Yes. We already had found it but this is not the only case. Searching deeper, will publish update within couple of days. Sincerely yours, Vladimir Olenin, CEO UAE: +971 50 561 2296 RUS: +7 903 671 0081 Skype: vahvarh Telegram: @vahvarh PRONETCOM FZ-LLC UAE, Dubai, Dubai Internet City, bld 14, office 206 Russia, Moscow, Aleksandra Solzhenitsyna street, bld 23A … On 26 Jan 2024, at 04:53, AHA @.***> wrote: Hi, It could be the socket.cc function JS_METHOD(_receive_strict) experienced a memory leak — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJCEPQZBYG4JSHIKONMPW3YQL5AHAVCNFSM6AAAAABCDWMEHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRGIZTQNZZGU. You are receiving this because you commented.

Thank you, looking forward to it!