Is it safe to realloc memory allocated with new?

by

You can only realloc that which has been allocated via malloc (or family, like calloc).

That’s because the underlying data structures that keep track of free and used areas of memory, can be quite different.

It’s likely but by no means guaranteed that C++ new and C malloc use the same underlying allocator, in which case realloc could work for both. But formally that’s in UB-land. And in practice it’s just needlessly risky.

C++ does not offer functionality corresponding to realloc.

The closest is the automatic reallocation of (the internal buffers of) containers like std::vector.

The C++ containers suffer from being designed in a way that excludes use of realloc.

Instead of the presented code

int* data = new int[3];
//...
int* mydata = (int*)realloc(data,6*sizeof(int));

… do this:

vector<int> data( 3 );
//...
data.resize( 6 );

However, if you absolutely need the general efficiency of realloc, and if you have to accept new for the original allocation, then your only recourse for efficiency is to use compiler-specific means, knowledge that realloc is safe with this compiler.

Otherwise, if you absolutely need the general efficiency of realloc but is not forced to accept new, then you can use malloc and realloc. Using smart pointers then lets you get much of the same safety as with C++ containers.

More Related Contents:

  1. Why is there no reallocation functionality in C++ allocators?
  2. Dynamic memory allocation in game server [closed]
  3. How do malloc() and free() work?
  4. What is the difference between new/delete and malloc/free?
  5. Is delete[] equal to delete?
  6. C++ new int[0] — will it allocate memory?
  7. How could pairing new[] with delete possibly lead to memory leak only?
  8. Compelling examples of custom C++ allocators?
  9. How to get available memory C++/g++?
  10. Will new return NULL in any case?
  11. How does a C++ reference look, memory-wise?
  12. Any reason to overload global new and delete?
  13. Making std::vector allocate aligned memory
  14. Are memory leaks “undefined behavior” class problem in C++?
  15. Does delete on a pointer to a subclass call the base class destructor?
  16. What happens when you deallocate a pointer twice or more in C++?
  17. Check if a pointer points to allocated memory on the heap
  18. What is the behavior of “delete” with stack objects? [duplicate]
  19. Reason why not to have a DELETE macro for C++
  20. Using realloc to shrink the allocated memory
  21. How is heap and stack memories managed, implemented, allocated?
  22. Does this type of memory get allocated on the heap or the stack?
  23. How do I call the original “operator new” if I have overloaded it?
  24. Is global memory initialized in C++?
  25. What does “Memory allocated at compile time” really mean?
  26. When do programmers use Empty Base Optimization (EBO)
  27. vector memory allocation strategy
  28. Memory management patterns in C++
  29. The difference between delete and delete[] in C++ [duplicate]
  30. Are data members allocated in the same memory space as their objects in C++?

Leave a Comment