Posted By: The Channel 9 Team | Jun 28th, 2005 @ 4:18 PM | 96,528 Views | 31 Comments
Charles Torre (interviewer) and Michael Lehman (cameraman) continue the "Going Deep: Windows" series with a discussion with Landy Wang, a developer of the oh so important Windows Memory Manager.

Sorry for the low audio volume.

EDIT November 2, 2008: There is no streaming video for this interview. We will look into it. For now, please click here.
Tags: Kernel, OS
Media Downloads:
Rating:
2
0
Charles
Charles
Welcome Change
I actually asked about exception surfacing, which is distinct from the notion of handling. As poorly stated as the question was, I was really just trying to find out what the MM does when something goes "boo!" way down there as it relates to memory. I guess it makes sense that such a low level system wouldn't package up a Problem and send it up, but certainly, the MM is an aware system, as it relates to memory. Hey, I'm learning too! Smiley

C
YAY!  You got Landy!

Landy is one of the two or three Microsoft developers I've interacted with who NEVER gets things wrong.

Which is a remarkable statement if you think about it.  Most people I work with are falible. 

IME, Landy isn't.

Very educational!

Good work, thank you.
Interesting and something tells me that Windows would be a lot more stable if everybody moved to managed code.
koorb wrote:
Interesting and something tells me that Windows would be a lot more stable if everybody moved to managed code.


Three things wrong with that

1. What does it have to do with this topic?
2. Is Windows unstable?
3. If your cheap hardware is making Windows unstable how would managed code help that?
leighsword
leighsword
LeighSword
i used to do something like this,
     HLOCAL hMem = HeapAlloc(GetProcessHeap(),HEAP_ZERO_MEMORY, HUGE_SIZE);
...
     HeapFree(GetProcessHeap(), 0, hMem);

this way is faster than managed code MUCH, and never be wrong.
koorb wrote:
Interesting and something tells me that Windows would be a lot more stable if everybody moved to managed code.


And where would the managed code get it's memory?

Also, you can still leak memory in 100% managed code.
Manip wrote:


Three things wrong with that

1. What does it have to do with this topic?
2. Is Windows unstable?
3. If your cheap hardware is making Windows unstable how would managed code help that?


Like the who video was about memory management. And managed code has its own garbage collector.
All this talk of food is making my hugry...
Microsoft Communities