Home/ Questions/Q 4123104
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T23:34:07+00:00

This is an extension of my previous question, Application crash with no explanation .

  • 0

This is an extension of my previous question, Application crash with no explanation.

I have a lot of crashes that are presumably caused by heap corruption on an application server. These crashes only occur in production; they cannot be reproduced in a test environment.

I’m looking for a way to track down these crashes.

Application Verifier was suggested, and it would be fine, but it’s unusable with our production server. When we try to start it in production with application verifier, it becomes so slow that it’s completely unusable, even though this is a fairly powerful server (64-bit application, 16 GB memory, 8 processors). Running it without application verifier, it only uses about 1 GB of memory and no more than 10-15% of any processor’s cycles.

Are there any other tools that will help find heap corruption, without adding a huge overhead?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Use the debug version of the Microsoft runtime libraries. Turn on red-zoning and get your heap automatically checked every 128 (say) heap operations by calling _CrtSetDbgFlag() once during initialisation.

    _CRTDBG_DELAY_FREE_MEM_DF can be quite useful for finding memory-used-after-free bugs, but your heap size grows monitonically while using it.

    • 0