GoWork | Go Library for distributing work to workers | Architecture library

There are lots of easier of ways doing this but that is not your question. To be able to say where is the problem in your code we need to see the webpage source code. So without it i am going to make a guess.

Compiling shared libraries is broken with -no-pie, which should be a noop in this case.

Turns out there is nothing wrong with my code per se.Calling free() after a malloc() releases memory on the heap to be reused by the program but that does not mean it goes back to the system. The reason for this is still a bit out of my understanding.

Valgrind was not reporting memory leaks because there are none.

After doing dome research, reading more about the nature of dynamic memory allocation and landing here:

Force free() to return malloc memory back to OS

Why does the free() function not return memory to the operating system?

Will malloc implementations return free-ed memory back to the system?

Memory not freed after calling free()

Calling malloc_trim() after each free was enough to make the system reclaim the allocated memory.

For example, without calling malloc_trim(), CPU and memory usage of my program looks like this: On each call to my "reader" thread (first peak in CPU ussage) some memory is allocated. Calling mu "consumer" threads free the requested memory but the memory is not always returned to the system as per the blue line in the plot.

With malloc_trim() after each free(), memory usage looks how I was expecting it to look: When "reader" thread is executing memory associated with the porcess increases. When "consumers" are running, memory is freed and returned to the OS.

There's more you can refactor here but basically yes you move the lifting to a module and thanks to @Amadan, you can

go get trying to find the package docker_test/mult into /go path. But, you have copied into /go/src/app. That's why go get can't find the package locally and assumes the package is from remote repository, eg, github, and throws error import path does not begin with hostname. So copy the docker_test/mult inside /go path.

Another concern is, when you use WORKDIR go/src/app, it creates go/src/app inside /go path, So finally the path becomes /go/go/src/app. So use absolute path ie, WORKDIR /go/src/app.

Try this dockerfile:

According to your folder layouts, I guess your local $GOPATH is /gowork folder. In golang docker image, its $GOPATH is /go folder.

You have to create the docker file in this location /gowork/src/Dockerfile, then put the following in it. It works fine in my environment with your code.

for(;!endWork;){printf("work\n");} The program works well ! What is my error ?

Since the variable endWork is a regular variable, compiler with high optimization option (i.e. -O3) might assume the variable does not change and optimize out the read inside the loop, i.e. it transforms the loop:

Inventing new syntax tends not to work that well in practice. Use system() to run external commands from Vim, not backticks. Also set in Vim is weird, it doesn't evaluate RHS the way you expect. Most of the time it's a lot simpler to use let &option = ... instead of set option=....

Anyway, to answer your question, you don't need to run find(1) for that, plain Vim functions are enough for what you want:

If you meant the environment variable "temp", then you should do it as: