
Google Chrome won’t run properly on my work PC. Whenever it loads, I get the sad folder saying, “Aw, Snap!” No matter whether I’m trying to access a local html file, a local image, or a remote site, I always get the same result.
Update: It turns out that there’s a conflict between Chrome and Symantec Endpoint Protection. Adding --no-sandbox to the command line bypasses the bug. It’s not a great solution, but it’s got chrome working on my work PC for now.
Update 2: Here’s Symantec’s current official response.
Google released their new static maps API a few days back, and it prompted me to finally dig into their tools a bit to see what I could accomplish. I still didn’t get into the real API, but the static API provided a bit of entertainment. The developer’s guide answered all of my questions, and I was easily able to create the map to my house attached to this post. There’s also a wizard that can be used if you don’t want to read the docs. Also interesting: the real maps API and mapplets.
Chris posted this recently, and I just had to share it. For my use, however, I’d like to see the space bar be a little taller. 
Comments Off