Executable Archaeology: The Case Of The Stupid Thing Eating All My RAM

I would like to see the bug report. "BUG12345: Shaking my computer results in a loss of available memory".

I find it incredible that Microsoft would allow OEMs to preload software like this. The end user experience and impression of Windows 8 takes a brutal hit.

Very neat discovery and great write-up about it! Were you able to get in touch with somebody at "Spacer" to let them know about the mistake? If so, are they going to correct it?

Why protect the guilty "Spacer"?

A perfect example of why you should never use foul language in your code - even if it's not meant for production ;)

Interesting article. There are better ways of looking at memory allocations in .NET code, however, including CLR allocation profiler, WinDBG, VMMap, and tools from Telerik, Jetbrains, ANTS etc that take away a lot of the guess work. Still, kudos to the author for not doing an immediate re-pave.

Thank you. This was a fun read.

To the author: Saw this on comex's Twitter and got a good kick out of it. My first surprise was that HN didn't already have this submitted. My second was it reaching first page in 3 hours.<p>:)

If I were you I would be thankful that there were memory issues, otherwise you wouldn't even have discovered this malware! :)

Am I the only one who thinks this is <i>obviously</i> a ploy to sell more RAM to the <i>angry</i> users!?!@?