Question: I'm searching for pointers to structs in the memory of a program, that are 4 bytes away from each other, but the amount can vary. I'm pretty sure that after the structs comes some other variable that's not a pointer.

I figured if I tried to use that next variable as a pointer and apply to it the highest offset the struct I'm looking for can have, GetProcessMemory(I'm doing this in c++ btw) would fail, and I'd know it's not the thing I'm looking for and that the "list" of pointers to structs I'm looking for ends there.

But that seems unreliable since it could happen that that next variable would have a value that pointed to another valid struct and GetProcessMemory would **NOT** fail, so I'm asking if there's a better way.

CheatEngline seems to do it pretty flawlessly, so what am I missing?

Thank you in advance.

Answer: 
GCS provides strong read-after-write consistency. If you upload a new version of an object and then download it back, you will always get the new version of the object.

However, by default, when a publicly readable object is fetched, GCS responds with a "Cache-Control" header allowing caching for up to 1 hour. Google itself, your web browser, or some firewall between you and Google may decide based on that header to cache your object. You can check to see if this is the problem by fetching the object again and tacking some bogus URL parameter onto the end of the request, like "?avoidTheCaches=1".

You can prevent this from happening by setting the object's "cacheControl" property to something like "private" or "max-age=0". You can set this property as part of an upload. You can also modify the property for an existing object, but if the resource has already been cached, you'll have to wait out the hour before you'll see the new version.
You can go to the object in your console, click on "Edit Metadata", then enter what you want in the "Cache control" field. If you want no caching at all, you can add the string `no-store`.

Documentation on the allowed values is [here](https://cloud.google.com/storage/docs/metadata#cache-control).