What’s the differences between VirtualAlloc and HeapAlloc?

by

Each API is for different uses. Each one also requires that you use the correct deallocation/freeing function when you’re done with the memory.

VirtualAlloc

A low-level, Windows API that provides lots of options, but is mainly useful for people in fairly specific situations. Can only allocate memory in (edit: not 4KB) larger chunks. There are situations where you need it, but you’ll know when you’re in one of these situations. One of the most common is if you have to share memory directly with another process. Don’t use it for general-purpose memory allocation. Use VirtualFree to deallocate.

HeapAlloc

Allocates whatever size of memory you ask for, not in big chunks than VirtualAlloc. HeapAlloc knows when it needs to call VirtualAlloc and does so for you automatically. Like malloc, but is Windows-only, and provides a couple more options. Suitable for allocating general chunks of memory. Some Windows APIs may require that you use this to allocate memory that you pass to them, or use its companion HeapFree to free memory that they return to you.

malloc

The C way of allocating memory. Prefer this if you are writing in C rather than C++, and you want your code to work on e.g. Unix computers too, or someone specifically says that you need to use it. Doesn’t initialise the memory. Suitable for allocating general chunks of memory, like HeapAlloc. A simple API. Use free to deallocate. Visual C++’s malloc calls HeapAlloc.

new

The C++ way of allocating memory. Prefer this if you are writing in C++. It puts an object or objects into the allocated memory, too. Use delete to deallocate (or delete[] for arrays). Visual studio’s new calls HeapAlloc, and then maybe initialises the objects, depending on how you call it.

In recent C++ standards (C++11 and above), if you have to manually use delete, you’re doing it wrong and should use a smart pointer like unique_ptr instead. From C++14 onwards, the same can be said of new (replaced with functions such as make_unique()).

There are also a couple of other similar functions like SysAllocString that you may be told you have to use in specific circumstances.

More Related Contents:

  1. Why should C++ programmers minimize use of ‘new’?
  2. Recommendations for a heap analysis tool for Java? [closed]
  3. Exporting functions from a DLL with dllexport
  4. How can a Win32 process get the pid of its parent?
  5. How do I send key strokes to a window without having to activate it using Windows API?
  6. Arrays, heap and stack and value types
  7. How to write hello world in assembler under Windows?
  8. GetWindowRect returns a size including “invisible” borders
  9. What is the difference between the `A` and `W` functions in the Win32 API?
  10. Creating a thread in DllMain?
  11. Vista/7: How to get glass color?
  12. How can I mute/unmute my sound from PowerShell
  13. Building libcurl with SSL support on Windows
  14. Removing window border?
  15. Alignment requirements for atomic x86 instructions vs. MS’s InterlockedCompareExchange documentation?
  16. Java Refuses to Start – Could not reserve enough space for object heap
  17. Why would you ever want to allocate memory on the heap rather than the stack? [duplicate]
  18. What are uses of the C++ construct “placement new”?
  19. Win32: full-screen and hiding taskbar
  20. How to make a keyboard hook global across processes
  21. How do I detect the DLLs required by an application?
  22. How to write hello world in assembly under Windows?
  23. What’s the relationship between “a” heap and “the” heap?
  24. Is it possible programmatically add folders to the Windows 10 Quick Access panel in the explorer window?
  25. EditText causing memory leak
  26. How do you set the glass blend colour on Windows 10?
  27. Why doesn’t delete destroy anything?
  28. Steps in the memory allocation process for Java objects
  29. Programmatically prevent Windows screensaver from starting
  30. How do I capture the audio that is being played?

Leave a Comment