ios-base | Boilerplate for new iOS projects using Swift | iOS library

It seems like you have a few mistakes. First one, in here:

cout is tied to cin, not the other way around.

cout being tied to cin means cout is flushed automatically when reading from cin.

cout.tie(nullptr); would be pointless, as cout.tie() is already nullptr.

NULL is an equivalent of 0. The C++ type-safe way to express a null pointer is nullptr.

You're misusing Axios API. In GET requests, only one parameter - config object - should be passed into the corresponding method, and params should be passed inside params property of that object. Like this:

From [ios.members.static]/2:

Effects: If any input or output operation has occurred using the standard streams prior to the call, the effect is implementation-defined. Otherwise, called with a false argument, it allows the standard streams to operate independently of the standard C streams.

Furthermore, the cppreference page notes that

If this function is called after I/O has occurred on the standard stream, the behavior is implementation-defined: implementations range from no effect to destroying the read buffer.

I'm not entirely sure what exactly happened in your case. Reading the source of libstdc++ (e.g., here), which I assume is the standard library being used, it seems that it clears the buffers. This means that it's possible that some input you were waiting for was buffered, and your program either started reading from a strange spot or the reads just failed entirely. But the precise details and why that would have caused an out of memory error is beyond me.

(It's also worth noting that the fact you're calling it in a loop doesn't seem to be the problem in this implementation, as libstdc++ only clears the buffers if you're already unsynchronised with stdio.)