Some windows can be irrevocably lost when mDesktop crashes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Place three different windows on each of 9 different desktops
2. Manually crash mDesktop.exe using TaskMgr.exe
3. Restart mDesktop

What is the expected output? What do you see instead?
It is expected that ALL of the windows will come back; however, often only 
certain applications come back while others do not. For instance, in the most 
recent instance that this happened, all windows from ALL threads that were on 
the active desktop when mDesktop crashed were still available (including a 
couple of Google Chrome windows, some Comodo dragon windows, some Notepad, 
etc.) However, SOME of the threads on SOME of the other windows were "lost" and 
cannot be retrieved: although EVERY ONE of the Comodo Dragon windows returned 
from all desktops, none of the Google Chrome, Windows Explorer or Notepad 
windows that were not on the active desktop came back. The threads, however, 
are definitely still running and responsive (because if you try to shut down, 
for instance, a "Save" dialog will come up for unsaved Notepad content; the 
Google Chrome windows still show up and act responsively from within the Chrome 
Task Manager, etc.)

What version of the product are you using? On what operating system?
Windows 7 64-bit Home Edition running mDesktop 1.6b3

Please provide any additional information below.
This is a critical issue for me. I love mDesktop but I'm losing some of my work 
to hidden windows.

Original issue reported on code.google.com by mcd...@gmail.com on 7 Apr 2012 at 6:07

[GoogleCodeExporter]

Strangely enough, when I compiled a new copy from the latest source (just now) 
and ran that to restore lost windows, it actually DID restore every missing 
window from all desktops with the sole exception of Google Chrome windows whose 
processes had crashed. Those Chrome windows should have been saved even without 
their processes, because the Chromium source base DOES have support for that 
(since Comodo's windows were saved), but I'm not going to get picky. Ultimately 
it looks like the latest version handles this issue somehow.

Original comment by mcd...@gmail.com on 7 Apr 2012 at 6:26