chrome and "aw, snap!" frequency

[Nikos Vassiliadis]

Hi,

I am using chromium since a few months as my main browser.
It's nice and seems fast. Firefox is the other choice but
it feels much slower.

I am a bit off put by the frequency of crashes (which might
be ten per hour of use). I don't mind re-loading a page that
has crashed but I do mind losing input I typed in:)

Running it from a terminal shows several stack traces, warnings(?),
errors(?) etc.

So, does it behave for you people?

> [nik at moby ~]$ script chrome_log.txt chrome
> Script started, output file is chrome_log.txt
> [5464:402678784:1110/223239:ERROR:battery_status_manager_default.cc(22)] Not implemented reached in virtual bool device::<anonymous namespace>::BatteryStatusManagerDefault::StartListeningBatteryChange()
> Received signal 11 SEGV_MAPERR 000000000000
> #0 0x0000008f798a <unknown>
> #1 0x000809d6c947 <unknown>
> #2 0x000809d6c158 <unknown>
> [end of stack trace]
> Received signal 11 SEGV_MAPERR 000000000000
> #0 0x0000008f798a <unknown>
> #1 0x000809d6c947 <unknown>
> #2 0x000809d6c158 <unknown>
> [end of stack trace]
> [5464:402678784:1110/223300:ERROR:battery_status_manager_default.cc(26)] Not implemented reached in virtual void device::<anonymous namespace>::BatteryStatusManagerDefault::StopListeningBatteryChange()
> Received signal 11 SEGV_MAPERR 000000000000
> #0 0x0000008f798a <unknown>
> #1 0x000809d6c947 <unknown>
> #2 0x000809d6c158 <unknown>
> [end of stack trace]
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> Received signal 11 SEGV_MAPERR 000000000000

My environment is a common one, 10-STABLE amd64, mostly
up-do-date binary packages.

Thanks in advance, Nikos