C Utility code review and memory leak detection/resolution
Budget: $8 – $15 USD
As a project owner, I am currently facing an unusual increase in memory consumption by a piece of hardware-dependent C software that I am developing. The primary functional requirement is memory leak detection. It has already been observed that the issue tends to occur specifically during multi-threading (located in located in heap).
It is probably related to incorrect use of the libcurl library in threads.
Key tasks include:
- Identifying the origin of the memory leak in the multi-threading portion of the utility.
- Resolving the issue to prevent unusual memory consumption and potential future crashes.
- Ensuring seamless operation of the memory leak detection function after the problem is addressed.
- Reveal and explain my faults.
Desirable skills for interested freelancers include:
- Experience with C and multi-threading.
- Profound understanding and capability to use Curlib and json-c libraries. Especially sharing curl instance between threads for lover memory consumption (curl_easy_init vs curl_share_init between threads).
- Proven capacity to identify and fix memory leaks in C programs. (we can use valgrind, but I don't work with it because of threads).
It is probably related to incorrect use of the libcurl library in threads.
Key tasks include:
- Identifying the origin of the memory leak in the multi-threading portion of the utility.
- Resolving the issue to prevent unusual memory consumption and potential future crashes.
- Ensuring seamless operation of the memory leak detection function after the problem is addressed.
- Reveal and explain my faults.
Desirable skills for interested freelancers include:
- Experience with C and multi-threading.
- Profound understanding and capability to use Curlib and json-c libraries. Especially sharing curl instance between threads for lover memory consumption (curl_easy_init vs curl_share_init between threads).
- Proven capacity to identify and fix memory leaks in C programs. (we can use valgrind, but I don't work with it because of threads).