Issue metadata
Sign in to add a comment
|
All extensions crash on Debian
Reported by
jidanni@gmail.com,
Feb 27 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.74 Safari/537.36 Steps to reproduce the problem: All extensions crash on Debian with chromium 65 To reproduce: On Debian: 1. Install chromium 65 2. Install some extensions, like adblockplus, etc. Received signal 11 SEGV_MAPERR 0000ffffff00 #0 0x55a3e8a8537e <unknown> ... #5 0x7fb35cc3914a std::__cxx11::basic_string<>::compare() ... [end of stack trace] Calling _exit(1). Core file will not be generated. What is the expected behavior? What went wrong? Filed with downstream too, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890954 WebStore page: Did this work before? Yes 64 Chrome version: 65.0.3325.74 Channel: n/a OS Version: Flash Version:
,
Feb 28 2018
Unable to reproduce this issue on reported version 65.0.3325.74 using Ubuntu 14.04. Installed 65.0.3325.74 and installed adblock plus and no crash is seen. Attaching screencast for reference. As per comment#0 this might be specific to Debian. As ET Team doesn't have debian machine could someone from Inhouse team please have a look at this issue. Thanks!
,
Feb 28 2018
Package: chromium Version: 65.0.3325.74-1+b1 -- System Information: Debian Release: buster/sid APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii chromium-common 65.0.3325.74-1+b1 ii libasound2 1.1.3-5 ii libatk-bridge2.0-0 2.26.1-1 ii libatk1.0-0 2.26.1-3 ii libavcodec57 7:3.4.2-1+b1 ii libavformat57 7:3.4.2-1+b1 ii libavutil55 7:3.4.2-1+b1 ii libc6 2.27-0experimental1 ii libcairo2 1.15.10-2 ii libcups2 2.3~b3-1 ii libdbus-1-3 1.13.0-1 ii libevent-2.1-6 2.1.8-stable-4 ii libexpat1 2.2.5-3 ii libflac8 1.3.2-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-2 ii libgcc1 1:8-20171016-1 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-0 2.55.2-2 ii libgtk-3-0 3.22.28-1 ii libharfbuzz0b 1.7.2-1 ii libicu57 57.1-8 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.18-1 ii libnss3 2:3.35-2 ii libopus0 1.2.1-1 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libpng16-16 1.6.34-1 ii libpulse0 11.1-4 ii libre2-4 20180201+dfsg-2 ii libsnappy1v5 1.1.7-1 ii libstdc++6 8-20171016-1 ii libvpx5 1.7.0-3 ii libwebp6 0.6.1-1 ii libwebpdemux2 0.6.1-1 ii libwebpmux3 0.6.1-1 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb1 1.12-1 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-1 ii libxdamage1 1:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.7+dfsg-1 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.29-5 ii libxss1 1:1.2.2-1+b2 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages chromium recommends: ii fonts-liberation 1:1.07.4-5 Versions of packages chromium suggests: pn chromium-driver <none> pn chromium-l10n <none> pn chromium-shell <none> pn chromium-widevine <none> -- no debconf information
,
Feb 28 2018
ID: cfohepagpmnodfdmjliccbbigdkfcgia crashed ID: cfhdojbkjhnklbpkdaibdccddilifddb crashed
,
Mar 1 2018
Unable to reproduce the issue on Linux Debian Rodate machine with chrome reported version-65.0.3325.74 and latest beta-65.0.3325.106.Able to add Adblock Plus,last pass & Office online extensions etc from chrome://apps with out any crash issue. Please check the issue on latest chrome versions with clean profile & let us know your observations on the same. Please find the attached screencast for reference . Thanks..!
,
Mar 1 2018
Thanks. I'll try on my very best machine tomorrow.
,
Mar 1 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 1 2018
Full stack trace attached. OK here's how I reproduced it. Following the instructions in https://wiki.debian.org/Chromium/Debugging I installed chromium-dbgsym: Installed: 65.0.3325.74-1+b1 and as user 'nobody' on a fresh account, first installed extension adblockplus, which promptly crashed. Now restarting the browser this time via chromium --debug 2>&1 | tee xgdb-chromium.txt I produced a trace wherein you can see in excruciating detail what happened. Now I cleaned out all of user nobody's files and started again with no extensions, which didn't crash. Attached is Normal*.txt for that case.
,
Mar 2 2018
Issue is not reproducible from ET team and Inhouse team based on comments#2 and comment#5. As issue is not reproducible from TE end removing requesting someone from Platform>Extensions team to have a look at this issue. Hence adding TE-NeedsTriageHelp label. Thanks!
,
Mar 2 2018
Thanks for opening the bug downstream. This only appears to be a problem on Debian, so I'm closing this issue. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Feb 27 2018