Home/ Questions/Q 383617
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T15:18:01+00:00

First I realize that leaks can fragment memory badly, but please bear with me.

  • 0

First I realize that leaks can fragment memory badly, but please bear with me.

  • Using WinDbg and attaching to a process: Using !heap (or another WinDbg command), what should I expect see if I’m dealing with memory fragmentation as opposed to a leak? For instance, I can use “!heap stat” and “!heap stat -h handle” to zero-in on the code generating a leak; but is there something in these same return values which would hint at fragmentation?
  • Has memory allocation changed radically between XP and Vista? Particularly, as related to DLL and other library-loading? We’ve been developing exclusively on XP so I’m unfamiliar with Vista, but it turns out that certain memory issues we’ve been seeing on XP disappear when we install the same binaries on Vista.

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I am sorry I can’t help you with the fragmentation issue, so I am only going to address your second question.

    Vista introduced ASLR which changes the way DLLs are loaded. For more info see this wiki entry and for a more specific discussion this post may be useful.

    • 0