dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: C++
Expertise: Advanced
Jan 28, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Dynamic Memory Allocations and Thread Safety

In general, the global new and delete operators are implemented in a thread-safe manner: each invocation of either operator locks the heap before performing the allocation/deallocation of memory and when the action is completed, the heap is unlocked. Thus, you can use new and delete safely in multithreaded applications. However, the thread-safety of new and delete imposes an unnecessary runtime overhead for single-threaded applications. Therefore, in time-critical single-threaded application, you may consider using alternative memory management schemes such as overloading new and delete for particular classes or using a custom memory pool.

Danny Kalev
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date