Google calls on developers to polish Chrome
That tinkering feeling
Google yesterday released an update to its Chrome web browser that fixes a number of known glitches and crashes in the software.
The search engine giant said Chrome 0.3.154.3 fixes a crash when using the spell check “add to dictionary” function, as well as a browser crash on tablet PCs running Microsoft Windows Vista.
Other notable fixes include a problem in the previous version with a video playback bug brought on by plug-in issues that caused the browser to hang.
Google’s also waving a version of its shiny new browser under the noses of developers who might be keen to fiddle with open-sourced Chrome, which remains in beta. The firm warned that 0.3.154.0 is strictly for the dev channel only.
It’s calling on testers to help flush out a few remaining bugs, mostly in handling SSL edge cases and HTTP authentication in Chrome’s upcoming new HTTP networking code.
Earlier this week Firefox released a beta of version 3.1 of its own open source browser, while Microsoft plugged several critical holes in Internet Explorer. ®
Oki - it works as a browser, it's pretty fast off the starting blocks... all good so far.
It's not as polished as Opera nor as extensible as Firefox - but it's better than IE (no great feat that though).
It dials home about every 5 minutes to check for updates using GoogleUpdate.exe - ok, fair enough - which runs as a process that always starts and seems to be damned hard to stop (oki, you can terminate the process but it always rises from the grave within the next 5 minutes or so) - not quite so good.
Should you decide to uninstall Chrome, once getting past the "cute" "is it something we said" message, GoogleUpdate remains on your system and continues to dial home for updates... even though it's no longer got anything to update... mmmmmkay.
So to remove GoogleUpdate you need to find it, and it's in a hidden application folder, manually delete the files and then fix the registry.
Chriminal? Oh... no, beta =\
re: Crash? Yes
"As opposed to every other browser where two instances are completely independent processes"
ITYM "as opposed to IE, where two instances started separately are multiple processes" - or you're using a far odder range of browsers than is normal. Neither Firefox nor Opera will allow you to start multiple instances in normal use (tho' Firefox does have the -no-remote command-line switch, or you can set MOZ_NO_REMOTE).
@ the other steve
"You can so polish a turd, if you dry it out a bit, then apply several coats of really thick varnish one after the other, allowing each to dry, and THEN polish the resulting plasticy mess. A bit like the fake bread/cake stuff infant schools used to have before they realised that infants would, in fact, still chew it, and paint and varnish are toxic".
For that, you sir win best digression of the week. Please report to your nearest bar for a beer on me.