Multipart processing existence of memory leakage

[fish-jade]

demo：https://github.com/fish-jade/crow-demo/tree/demo-cpp

Core upload code

When using crow::multipart::message to upload a file of about 88 MB, no processing will be done, and eventually there will be a memory leak.
Memory before upload:

Uploaded memory:

Use postman to upload debugging, as shown in the figure:

Please help check if it is a usage problem or a leak bug of crow itself, thank you very much~ ❤️❤️

[fish-jade]

No matter how long memory is never released, and there will be further memory increases after repeated requests for uploads.

[fish-jade]

Hello @gittiver , may I ask if you can preliminarily determine whether it is a bug or a use problem? And what can I do to move this issue forward faster?

[gittiver]

You could show that it is not a usage problem.
A second idea - have you checked that a complete request arrives at crow server - maybe a timeout happens?
if crow consumes memory, what arrives?

[fish-jade]

Thank you very much for your reply! @gittiver

I provided a minimal demo: https://github.com/fish-jade/crow-demo/tree/demo-cpp. At the moment I don't think it's a usage issue. As for the second idea, the request can reach the crow server normally and eventually return 200, but the handler in the crow server does not actually have any code with memory leaks (there is a core code map in my question).

I also compared other libraries such as cpp-httplib, rocket in rust, these two will also have memory growth but compared to crow will be less about 2-3M, crow memory growth on the first request will be more about 17M, subsequent multiple requests will grow by 2-3M.

I'm not sure if this is normal, other libraries also have memory growth and don't release it (but crow grows more than others).