Have a suggestion?

Click here to suggest a blog item.

Newsletters Archive

Catch up with DonationCoder by browsing our past newsletters, which collect the most interesting discussions on our site: here.

Editorial Integrity

DonationCoder does not accept paid promotions. We have a strict policy of not accepting gifts of any kind in exchange for placing content in our blogs or newsletters, or on our forum. The content and recommendations you see on our site reflect our genuine personal interests and nothing more.


Latest News

July 2, 2024
Server Migrations Coming

  • Donationcoder server migration is slowly proceeding, expect some hiccups as we get all our ducks in a row..

July 19, 2022
Software Update

Jan 3, 2022
Event Results

May 13, 2020
Software Updates

Mar 24, 2020
Mini Newsletter

Dec 30, 2019
Software Updates

Jan 22, 2020
Software Updates

Jan 12, 2020
Newsletter

Jan 3, 2020
Event Results

Jan 2, 2020
Software Updates

Dec 30, 2019
Software Updates

April 27, 2019
Software Updates

Feb 26, 2019
Software Updates

Feb 23, 2019
Software Updates

Feb 14, 2019
Software Updates

Jan 6, 2019
Event Results

Dec 2, 2018
Software Updates

Nov 13, 2018
Software Releases

July 30, 2018
Software Updates

June 24, 2018
Software Updates

June 6, 2018
Software Updates

Apr 2, 2018
Fundraiser Celebration

Apr 2, 2018
Software Updates

Feb 24, 2018
Software Updates

Jan 14, 2018
Major Site News

Jan 10, 2018
Event Results

Latest Forum Posts

Our daily Blog

This page spotlights the most interesting posts collected from our forum every day.

You are viewing a specific blog item. Click here to return to the main blog page.

Is this the holy grail to solving windows-out-of-resources bugs?

Screenshot - 7_26_2007 , 9_39_41 PM_thumb.png
This was posted on Ed Bott's blog today, and it talks about Vista but i think this is applicable for Win2k and Windows XP as well.  I have run into this problem before and it's caused me no end of pain when it happens (sometimes you don't even realize this is the cause but strange things start happening to your computer like programs refuse to open).  I am going to try this right away and i'm excited about it.

After opening a large number of programs and windows, you try to launch a new program or open a new browser tab or even switch back to an already running program and instead:
  • You get a strange “out of memory” message, despite the fact that you’re using only a fraction of the RAM installed on your system.
  • The window opens but its contents refuse to load.
  • The window opens, but menus are missing, dialog boxes are empty, or buttons don’t work.
...
The problem, as it turns out, is as old as the Windows NT family. I’ve found references to this issue that date back to the mid-1990s and Windows NT 3.1 and 3.5. The fix for Vista, just as for those much older versions of Windows, involves editing a key in the Windows Registry.

First the problem: Windows sets aside a blob of system memory called the desktop heap, which it uses to store user interface objects such as windows, menus, and hooks. The Microsoft Advanced Windows Debugging and Troubleshooting Blog offers a dense, but still readable explication of the problem and why it occurs (it’s a two-part series: read the Desktop Heap Overview first and if your eyes haven’t glazed over read the shorter Desktop Heap Part 2 for details that are specific to 64–bit Windows, systems with 3GB of RAM, and Windows Vista).

The fix for 32–bit Windows Vista is simple: The interactive desktop heap size needs to be bumped up to a value greater than its default setting of 3072KB.

http://blogs.zdnet.com/Bott/?p=269



Share on Facebook