The default interactive desktop heap size has been increased on 32-bit Vista SP1

re: The default interactive desktop heap size has been increased on 32-bit Vista SP1

Gerg — Fri, 21 Mar 2008 02:58:06 GMT

That's nice and all, but... Coming from a Unix background it still seems crazy that a shared per-session resource like this is impacting server processes at all. I mean, I could understand if we were using some kind of GUI toolkit resources like cursors or windows but if we're an entirely non-UI server process it seems like something's broken that it's using *anything* from this resource at all.

[Often Windows services use windows messages for communication, even if there isn’t a visible window. Sometimes services directly call the USER functions to do this, and other times the service depends on another library that in turn relies on USER. In either case, if the process depends on user32.dll, it will allocate from desktop heap. On the flip side, a process that does not depend on user32.dll will not use desktop heap.]

default interactive desktop heap size - no reg key?

Julian — Thu, 09 Oct 2008 14:48:03 GMT

Vista HP SP1 - I think I am having heap problems - screen not redrawing correctly (UAC dialog does not appear - mouse over invisible buttons gets them repainted but that's all; Firefox 3 toobars disappear; OED window mostly white, etc.) - but there is no such key in my registry.

Can it/should it be created? Are there other keys that should go with it if it is created?

re: missing key

Julian — Thu, 09 Oct 2008 14:50:51 GMT

Oops! Sorry, yes it is there: I was looking for a subkey not a value...

Exchange Client Extensions and Duet

Do What? — Wed, 15 Oct 2008 20:14:57 GMT

Exchange Client Extensions are used in Outlook to extend the functionality of Outlook.  A developer

re: The default interactive desktop heap size has been increased on 32-bit Vista SP1

Richard Voorheis — Mon, 10 Nov 2008 18:29:09 GMT

It is difficult to understand how the default Desktop Heap Size is causing printer driver DTM failure in "Print Processor API Test" at "Test Winprint print processor as User" task. Error "Status dll init failed".

Looks like I am chasing a wild goose here.