godebug | https : //github.com/derekparker/delve

The solution for this one is to simply increase the memory size in the istio-config.yaml file.
in my case, I'm updating the PVC and it looks like it's already filled with data and decreasing it wasn't an option for istio, so I increased it in the config file instead:

You've allocated C memory to hold many individual pointers. Each individual pointer can be set to a separate value. That's fine as far as it goes, but as you noted, the a[index] = box is a problem, because box itself holds a pointer to a Go-memory C.struct_Box.

I'm trying to add C Box to the array before passing it to a C function.

To do that literally, you need a C.malloc call. As written, you'll need one per C.struct_Box instance.

Would the fix for this be for me to write a function in C which can receive the array and the items needed to create the struct and I do that part in C instead?

While you could try that, it seems ... suboptimal.

I'm trying to minimise the number of calls to C so If I can create the array from Go that would be great. Really struggling with how to pass an array of data through to a function in C safely.

C is never really safe 😀 but I suspect your best bet here is to make use of the way C implements "arrays", which is as a sort of poor-man's slice. (Or, perhaps more accurately, a Go slice is a "C array" done right.) Remember that a slice is implemented in Go as a three-element header:

• pointer to base of storage area;
• current length within storage area; and
• capacity of storage area

which can then hold some run-time computed number n of items of some type. C's dynamic "arrays" work the same way, only without the safety of a proper slice header.

What this means is that you can write your C code—provided you have control of this C code—to take a pointer to a base of a storage area, and an int or size_t value that counts the number n of items in that area. The signature of such a function is:

You have a proxy interfering with your networking. The key is this message

As mentioned in the comments by JimB, the go profile is a sampling profiler and samples memory usage at certain intervals. In my case the sampling was not frequent enough to catch a function (JSON marshalling) that was using extensive amounts of memory.

Increasing the sample rate of the profiler by setting the environment variable

$ export GODEBUG=memprofilerate=1

Will updateruntime.MemProfileRateand the profile now includes every allocated block.

At last, found the problem,

The project should be first initialized using Project > Save Project As...

Instead of doing this, I created a new project file named MyGoProject.sublime-project manually, so the changes made in the file didn't reflect in Sublime.

If you define the CouchDB volume as you say, your host folder should be in /var/hyperledger/couchdb0.

You can always run docker volume ls and docker volume inspect your_volume_name to check the mount point of your volumes.

If you have not defined volumes for your container and you want to retrieve the folder (I think that's your problem), then try:

The simplest setup that disables HTTP/2 is

I found the solution here: cgo: Go pointers in Go memory The Registry Example (Alternative) solves my issue. Thanks.

go command documentation mentions that go examines some environment variables:

The go command, and the tools it invokes, examine a few different environment variables.

So, env variables are checked before the program starts, i.e in build time. When you set these variables from code, the program already runs.

It works from the IDE since the variables are applied before the compilation, therefore the code runs with all the changes you need.