Issue metadata
Sign in to add a comment
|
chromium #59 crashes during startup
Reported by
atrich...@gmail.com,
Jun 8 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Install (xubuntu) 16.04.2 LTS with updates as for 7th June 2017 - Chromium version 59 replaced 58 2. Start chromium-browser 3. It takes a SEGV during startup What is the expected behavior? Start the browser What went wrong? SEGV, fails to start. Install log, session backtrace and debug session with some info attached. $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 0000031d9a20 #0 0x0000b767cee3 base::debug::StackTrace::StackTrace() #1 0x0000b767c767 base::debug::StackTrace::StackTrace() #2 0x0000b767d2fe <unknown> #3 0x0000b77cac20 ([vdso]+0xc1f) #4 0x0000811dac1c <unknown> #5 0x0000811db9d8 <unknown> #6 0x000080ee32e8 <unknown> #7 0x000080edb5c3 <unknown> #8 0x000080edea72 <unknown> #9 0x0000b2c6699c BrowserContextKeyedServiceFactory::BuildServiceInstanceFor() #10 0x0000b3324146 KeyedServiceFactory::GetServiceForContext() #11 0x000080edeb66 <unknown> #12 0x000080e20e3e <unknown> #13 0x000080e21738 <unknown> #14 0x000081a9a25e <unknown> #15 0x000080e0bdc6 <unknown> #16 0x000080f8d5e2 <unknown> #17 0x000080f8dac5 <unknown> #18 0x0000b514ffcc content::StoragePartitionImplMap::Get() #19 0x0000b4de9259 <unknown> #20 0x0000b4de9ba7 content::BrowserContext::GetStoragePartition() #21 0x0000b4de9dc7 content::BrowserContext::GetDefaultStoragePartition() #22 0x000080f8a99e <unknown> #23 0x000080f8b284 <unknown> #24 0x000080f8b641 <unknown> #25 0x000080f8c537 <unknown> #26 0x000080f8c7ab <unknown> #27 0x000080e10ba3 <unknown> #28 0x000080e164bd <unknown> #29 0x000080e1678c <unknown> #30 0x000081ae9be0 <unknown> #31 0x000081053148 <unknown> #32 0x00008105408c <unknown> #33 0x0000b4ded0d9 content::BrowserMainLoop::PreMainMessageLoopRun() #34 0x0000b5147657 content::StartupTaskRunner::RunAllTasksNow() #35 0x0000b4dee76e content::BrowserMainLoop::CreateStartupTasks() #36 0x0000b4df37a3 <unknown> #37 0x0000b4dec252 content::BrowserMain() #38 0x0000b55295ee <unknown> #39 0x0000b0275adb service_manager::Main() #40 0x0000b5528140 content::ContentMain() #41 0x00008097bab7 <unknown> #42 0x00008097a08b <unknown> #43 0x0000b03c5637 __libc_start_main #44 0x00008097b8fe <unknown> gs: 00000033 fs: 00000000 es: 0000007b ds: 0000007b edi: 8410e63c esi: 8410e4a0 ebp: bfc0dea8 esp: bfc0dd70 ebx: 8410e2e8 edx: 00000006 ecx: 00000026 eax: bfc0dec0 trp: 0000000e err: 00000004 ip: 811dac1c cs: 00000073 efl: 00210282 usp: bfc0dd70 ss: 0000007b [end of stack trace] Calling _exit(1). Core file will not be generated. Crashed report ID: No, it does not get far enough to show a window or enable crash reporting How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes 58.0.3029.110 Built on Ubuntu , running on Ubuntu 16.04 Chrome version: 59.0.3071.86-0ubuntu0.16.04.1283 Channel: stable OS Version: 16.04.2 LTS / 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:28:22 UTC 2017 i686 i686 i686 GNU/Linux Flash Version: Shockwave Flash 25.0 r0 Using older v 58 to report this. Running with -debug offered me no help, most of the symbols were missing/anonymised. Aside: Annoyingly apt-get was unable to install v58 cos of codecs-ffmpeg* deps - I had to use dpkg with by-hand downloads to get my system back usable.
,
Jun 12 2017
Thanks for filing the issue, rechecked this issue on chrome version 59.0.3071.86 on Ubuntu 14.04 & Ubuntu 16.04 @ atrichoke: Can you please try "sudo apt-get update" . Then try a complete re installation of chrome. Please update us with your observations. Please help us with a crash ID if you able to view from chrome://crashes. Thanks.!
,
Jun 12 2017
Hi! - thanks for responding. OK, I did:
sudo apt-get update // usual output
sudo apt-get remove chromium-browswer chromium-browser-l10n chromium-codecs-ffmpeg-extra chromium-codecs-ffmpeg
sudo apt-get dist-upgrade // no changes
sudo apt-get install chromium-browswer chromium-browser-l10n chromium-codecs-ffmpeg-extra chromium-codecs-ffmpeg
which fetched v59 as before. Which failed as before - does not even start.
I also did the same with
sudo apt-get purge chromium-browswer chromium-browser-l10n chromium-codecs-ffmpeg-extra chromium-codecs-ffmpeg
sudo apt-get clean
sudo apt-get autoclean
sudo apt-get autoremove
before the reinstall. Same result, it doesn't even start.
If you mean some other way of complete re-installation, please say so - sorry
but apt-get and/or dpkg is the only means I know.
There might be add-ons which I don't know how to reinstall. Flash, AdBlock and suchlike.
Might they be preventing startup if there's an API inconsistency? Not my area of expertise
I'm sure you can tell.
Thanks again,
- Hugo (my real name)
,
Jun 12 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2017
Can you please check for all updates on Ubuntu and try updating it. Then reinstall chrome and try again. Thanks.!
,
Jun 13 2017
The ubuntu install was completely uptodate when it failed, and also yesterday when I
did a clean reinstall of chromium-browser. It's the xubuntu 16.04 LTE distro:
% cat /proc/version
Linux version 4.4.0-79-generic (buildd@lcy01-35) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #100-Ubuntu SMP Wed May 17 19:57:27 UTC 2017
% cat /proc/version_signature
Ubuntu 4.4.0-79.100-generic 4.4.67
% uname -a
Linux nc6320-lap1 4.4.0-79-generic #100-Ubuntu SMP Wed May 17 19:57:27 UTC 2017 i686 i686 i686 GNU/Linux
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
Cheers,
- Hugo
,
Jun 13 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 22 2017
Can you please update us on the behavior for the latest stable (59.0.3071.109) available.
,
Jun 22 2017
Hi, Well, this is embarrassing...
I was unable to test the latest stable (59.0.3071.109) because it seems not to have
been built yet for 32-bit i386 ubuntu 16.04 - I couldn't even find a .deb to install
it by hand. APT only has 59.0.3071.86 available, the one that failed on Jun 8th.
But as apt-get installed it anyway...
From [tools]->About Chromium
"Version 59.0.3071.86 (Developer Build) Built on Ubuntu , running on Ubuntu 16.04 (32-bit)"
now works fine on my xubuntu installs - there have of course been other updates to the
xubuntu environment since I reported the problem, too many to track. So I guess one of those
fixed it. How unfortunate, but OTOH good that it's all well now.
So it looks like it's fine with version 81 of the 4.4.0 kernel?
% cat /proc/version
Linux version 4.4.0-81-generic (buildd@lcy01-26) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #104-Ubuntu SMP Wed Jun 14 08:15:00 UTC 2017
% cat /proc/version_signature
Ubuntu 4.4.0-81.104-generic 4.4.67
% uname -a
Linux nc6320-lap1 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:15:00 UTC 2017 i686 i686 i686 GNU/Linux
Sorry to have bothered you - at least it looks like this won't recur with an uptodate system
now. You can mark this as fixed by other updates, thanks.
Thanks again for looking into this, Best Regards,
- Hugo
,
Jun 22 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 23 2017
Thanks a lot for the update provide, closing the issue. Please feel free to raise a new issue or reopen if observed again.
,
Jun 23 2017
Just for complete closure, the new version of chromium
59.0.3071.109-0ubuntu0.16.04.1289
turned up in the xubuntu channels the following day (today) and
it works fine. So all good.
I'd like to add that the new chromium 59.xxx... seems faster and more responsive than 58.xxx... - so thanks for that, love continuous improvement.
Thanks again,
- HUgo
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by atrich...@gmail.com
, Jun 8 2017