It appears that the latest official 3.3alpha and 3.2gamma images both 
have a significant, and perniciously dangerous, bug, which seemingly 
arrived in update 4897.

Until this bug is fixed, it is *very dangerous* to be using any image 
that has update 4897 in it, because each time you try to snapshot 
such an image ("save", "save and quit", etc.) you stand a good chance 
of losing the image.

Thus, ironically, the only way to assure that you won't lose such an 
image is never to save it.  Which however makes development work 
problematical.

Anyone who has not recently updated 3.3alpha past 4889 or updated 
3.2gamma2 past 4889 or started using 3.2gamma3 is advised to hold off 
on doing so.  Up-to-date 3.3a and 3.2gammaX images will all be in a 
very dangerous state in which to save them is potentially to lose 
them.

Stay tuned...

   -- Scott



PS:  Reverting method ProcessorScheduler class.idleProcess *appears* 
to circumvent the problem.