crashes every few days with SIGABRT in __libc_message() after upgrade to chrome version 49
Reported by
neal...@gmail.com,
Mar 22 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.37 Safari/537.36 Steps to reproduce the problem: 1. I can't discern any pattern yet other than upgrading to version 49 with the beta program. I'm just running as I have for a long time. What is the expected behavior? Don't crash What went wrong? Whole browser crashes Crashed report ID: b201817000000000 How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 50.0.2661.37 Channel: beta OS Version: Ubuntu 14.04.1 Flash Version: Shockwave Flash 21.0 r0 This has happened with the chrome beta since shortly after I upgraded to Chrome version 49 in January 2016. It crashes every few days, and I have 8 Ubuntu apport dump files since Feb 1, like apport/_opt_google_chrome-beta_chrome.1000-0.crash Here are a few more Crash IDs: 501b4f6000000000 147d92d000000000 1d5936d000000000 ba52d29000000000 75bb7fd800000000 b343013800000000 c36c287000000000 Let me know if there is an easy way to check for whether I also added any extensions around the end of January.
,
Mar 22 2016
I now see that while I'm on Chrome version 50.0.2661.37 now, I may not have seen the crashes since I moved with the beta to Chrome 50 on 2016-03-14. Crossing my fingers.....
,
Mar 30 2016
Stack Trace: ============ Thread 0 CRASHED [SIGABRT @ 0x000003e8000003f7 ] MAGIC SIGNATURE THREAD 0x00007fcc2df16cc9 (libc-2.19.so -raise.c:56 ) raise 0x00007fcc2df1a0d7 (libc-2.19.so -abort.c:89 ) abort 0x00007fcc2df53393 (libc-2.19.so -libc_fatal.c:175 ) __libc_message 0x00007fcc2dfeac9b (libc-2.19.so -fortify_fail.c:37 ) __fortify_fail 0x00007fcc2dfe9b5f (libc-2.19.so -chk_fail.c:28 ) __chk_fail 0x00007fcc2dfeabe6 (libc-2.19.so -fdelt_chk.c:25 ) __fdelt_chk 0x00007fcc33253e81 (libglib-2.0.so.0.4002.0 + 0x0008ce81 ) 0x00007fcbffffffff (.com.google.Chrome.Yn96zJ (deleted) + 0x0018bfff ) 0x00007fcbffffffff (.com.google.Chrome.Yn96zJ (deleted) + 0x0018bfff ) 0x00007fcc33254516 (libglib-2.0.so.0.4002.0 + 0x0008d516 ) 0x00007fcc25c0cf2c (liboxygen-gtk.so + 0x00119f2c ) 0x00007fcc25b928c8 (liboxygen-gtk.so + 0x0009f8c8 ) 0x00007fcc25b94fff (liboxygen-gtk.so + 0x000a1fff ) 0x00007fcc25ba3524 (liboxygen-gtk.so + 0x000b0524 ) 0x00007fcc367fb5af (chrome + 0x023455af ) 0x00007fcc2dfe892c (libc-2.19.so -clock_gettime.c:115 ) __clock_gettime This issue is seen from M17 - 17.0.963.46 which got broken in M41-41.0.2272.101 with 1 instance. Below link gives in details of the number of instances in which the crash has occurred for associated builds: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27raise%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-samplereports:5,productversion:1000 1.No crashes are seen on latest stable, beta, dev and canary channels 2.Last crash is observed on 49.0.2623.47 with single instance nealmcb@ - Please upgrade your chrome to latest beta M50-50.0.2661.49 and recheck for this issue by creating a new profile under chrome settings. Mostly this should resolve your issue. If issue still persists let us know will help you further. Thanks!
,
Mar 30 2016
Thank you for the feedback! I am on Version 50.0.2661.49 beta (64-bit), and I haven't seen this in the last two weeks.
,
Mar 31 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 19 2016
As per comment #4 closing this issue. Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by neal...@gmail.com
, Mar 22 2016