Fed up with Chrome almost always starting up with a complaint that it hadn't been shut down properly, I did a little Googling to see if the source of this problem could be identified. I found threads on this dating back years, with the most tried and true solution being to uninstall the browser, delete all its orphaned subdirectories, and start from scratch. Not having the time or inclination to subject myself to all that, I tried a secondary solution that involved deleting some .tmp files Chrome seems to have generated somewhere along the way. This seems to have mostly cured things, though I had a single incident since trying it. Hopefully this will stick, as it was a bit of a pain.

Links.tmp:	Thanks Ant and Mike Martinez and Acleacius.
Play:	Rebuild 2. Concerned Joe. Hanger 2.
Links:	5 Real Skills Video Games Have Secretly Been Teaching Us. The Five Most Annoying Sections of Video Games. Blackboards in Porn. Thanks Brian.
Science:	Scientists Sequence Genome of Ancient Plague Bacterium. Thanks Neutronbeam. Antigen-Fixed Leukocytes Tolerize Th2 Responses in Mouse Models of Allergy. Thanks TDW Geeks.
Images:	Borderlands Mad Moxxi Cosplay. It’s Not That Your Service Was Irrational... Married, But Already Cheating. Angry Birds IRL of the Day.
Media:	The Michael Bay Energy Drink. Walking Dead Season 2 Trailer.
The Funnies:	Hobbes And Bacon: Part 3. Thanks dakslf. Ultimate Cat Tree Cartoon - Savage Chickens.
Follow-up:	Carmack Prize Attempt - High Altitude Rocket On-board Video. Thanks Donovon. "Avengers" Trailer Causes Studio Confusion.