New issue
Advanced search Search tips

Issue 739659 link

Starred by 5 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 17
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chromium crashes instantly after launching (or after attaching a second desktop monitor)

Reported by joelmuku...@gmail.com, Jul 6 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Steps to reproduce the problem:
1. Start chromium
2. Attach second desktop monitor
3. Chromium crashes and won't launch again until I delete my personal settings in ~/.config/chromium/. I tried to disable hardware acceleration but that didn't work. Actually trying to change this setting (or even the "Automatically send usage statistics and crash reports to Google" setting) while the second monitor was attached also instantly crashes the browser.

What is the expected behavior?
That it doesn't crash upon launching, or upon attaching a second monitor.

What went wrong?
This is the error from the terminal:

$ chromium-browser 
[10267:10267:0706/110541.157224:ERROR:navigation_entry_screenshot_manager.cc(135)] Invalid entry with unique id: 9
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7fa201d9d425 base::debug::StackTrace::StackTrace()
#1 0x7fa201d9d80b <unknown>
#2 0x7fa2020c8390 <unknown>
#3 0x557192525dc8 <unknown>
#4 0x557192528656 <unknown>
#5 0x557192528df9 <unknown>
#6 0x557192529143 <unknown>
#7 0x7fa201e18821 <unknown>
#8 0x7fa201d9eeea base::debug::TaskAnnotator::RunTask()
#9 0x7fa201dc7e90 base::MessageLoop::RunTask()
#10 0x7fa201dc997d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7fa201dca83d <unknown>
#12 0x7fa201dcb300 base::MessagePumpLibevent::Run()
#13 0x7fa201dc6f15 base::MessageLoop::RunHandler()
#14 0x7fa201df1628 base::RunLoop::Run()
#15 0x7fa201e1de36 base::Thread::ThreadMain()
#16 0x7fa201e18726 <unknown>
#17 0x7fa2020be6ba start_thread
#18 0x7fa1eb76d3dd clone
  r8: 000000000000002e  r9: 0000557193f7c6ec r10: 0000000000000000 r11: 00007fa1eb7faf50
 r12: 00007fa1366faff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007fa1366faeb0
  di: 0000000000000000  si: 00007fa1366faeb0  bp: 00007fa1366faf00  bx: 00007fa1366faeb0
  dx: 000000000000005c  ax: 0000000000000000  cx: 00007fa184052760  sp: 00007fa1366fae60
  ip: 0000557192525dc8 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: Version 59.0.3071.109 (Developer Build) (64-bit)  Channel: stable
OS Version: 16.04
Flash Version:
 
Seeing what appears to be the same crash on my system:
Lenovo ThinkPad T440P
  - sda=Windows7 (original disk)
  - sdb=Ubuntu   (ssd)
$ uname -a
Linux irbt-5977 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ chromium-browser --version
Chromium 59.0.3071.109 Built on Ubuntu , running on Ubuntu 16.04
---
Able to get around it and restart using: chromium-browser --disable-extensions
---
Problem showed up after updates yesterday (05-JUL-2017)

Comment 2 Deleted

Comment 3 by pe...@my-portal.se, Jul 6 2017

I get the same error since today. Works if do not sign in to my profile or disable extensions. But only using single screen on laptop.

Lenovo Yoga 900, 
Chromium 59.0.3071.109 Built on Ubuntu , running on LinuxMint 18.2
Linux risa-mint 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Also tried with Kernel 4.8.0-58 but no difference.
Seeing the same error on my system. 

rm -r ~/.config/chromium let me (temporarily) sidestep the issue, but I suspect that a recent chromium update is causing this bug.

I'm also running linux (ubuntu 16.04 LTS) on a Lenovo machine (X1 Carbon 2nd ed.) 

Comment 5 by fof...@gmail.com, Jul 7 2017

Also receiving this error on my system. 
$ uname -a
Linux hydrogen 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ chromium-browser --version
Chromium 59.0.3071.109 Built on Ubuntu , running on Ubuntu 16.04

I am too running on a Lenovo machine (IdeaPad U330T) on Ubuntu 16.04 LTS. Disabling extensions seems to fix the problem, but the problem did not appear until the last update.
More info based off of others people's experience.. I'm also running on a Lenovo (T470s). I experienced the same issue with extensions installed and with a freshly installed browser with no extensions installed. 
This has been happening to me as of a few days ago. Running Linux Mint 18.1 Cinnamon v. 3.2.7 64 bit on a Thinkpad T420.

Am able to get around it by using chromium-browser --disable-extensions.

Crashes happened on existing install of Chromium as well as fresh install.

____

chronus@chronus-ThinkPad-T420 ~ $ chromium-browser
PPAPI flash has config file in /etc, but library does not exist and won't be used. Package is uninstalled, not purged.
[2603:2652:0707/224105.455652:ERROR:cache_storage_cache.cc(1450)] Cache size: 1193977 does not match size from index: 1198905
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f2307d59425 base::debug::StackTrace::StackTrace()
#1 0x7f2307d5980b <unknown>
#2 0x7f2308084390 <unknown>
#3 0x55635b7c2dc8 <unknown>
#4 0x55635b7c5656 <unknown>
#5 0x55635b7c5df9 <unknown>
#6 0x55635b7c6143 <unknown>
#7 0x7f2307dd4821 <unknown>
#8 0x7f2307d5aeea base::debug::TaskAnnotator::RunTask()
#9 0x7f2307d83e90 base::MessageLoop::RunTask()
#10 0x7f2307d8597d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f2307d8683d <unknown>
#12 0x7f2307d87300 base::MessagePumpLibevent::Run()
#13 0x7f2307d82f15 base::MessageLoop::RunHandler()
#14 0x7f2307dad628 base::RunLoop::Run()
#15 0x7f2307dd9e36 base::Thread::ThreadMain()
#16 0x7f2307dd4726 <unknown>
#17 0x7f230807a6ba start_thread
#18 0x7f22f17293dd clone
  r8: 000000000000002e  r9: 000055635d2196ec r10: 0000000000000000 r11: 00007f22f17b6f50
 r12: 00007f2288cd6ff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f2288cd6eb0
  di: 0000000000000000  si: 00007f2288cd6eb0  bp: 00007f2288cd6f00  bx: 00007f2288cd6eb0
  dx: 000000000000006c  ax: 0000000000000000  cx: 00007f223c0323a0  sp: 00007f2288cd6e60
  ip: 000055635b7c2dc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Cc: pnangunoori@chromium.org
Labels: TE-NeedsTriageFromMTV
Tested on Chromium  #59.0.3071.0 on Ubuntu 16.04(Desktop machine) and unable to reproduce the issue. Adding the label ‘TE-NeedsTriageFromMTV’ as 16.04 Ubuntu laptop is not available with us. Could someone from MTV please look into this issue.
Cc: pbomm...@chromium.org
I see you're running the chromium-browser that ships with Ubuntu.  Could you either
1. File a bug with Canonical.  (It's impossible for Google to get crash reports with Chromium)
2. Try with google-chrome-stable and if it still crashes, post the crash ID
Labels: Needs-Feedback
I tried 2 and can't reproduce the issue with google-chrome-stable. But about reproducing, it seems that the issue occurs occurs on Lenovo laptops and Chromium 59.0.3071.109.  
Project Member

Comment 12 by sheriffbot@chromium.org, Jul 17 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pbommana@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
Project Member

Comment 13 by sheriffbot@chromium.org, Jul 17

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment