Your message dated Sat, 20 Jul 2019 20:02:00 -0400
with message-id 
<CANTw=mnbbwc-tttn+fbcomujbw5iwac9+c8z8phcxkkce9o...@mail.gmail.com>
and subject line Re: Bug#932567: Found the issue
has caused the Debian Bug report #932567,
regarding chromium: extremly slow startup and operation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
932567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932567
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 76.0.3809.62-1
Severity: important
Tags: a11y

Dear Maintainer,

Chromium does startup extremly slow (like 2 min before I can enter a URL).
After each action like opening a new tab, surfing to an url, opening settings
page and so on I have to wait again somthing like 2 minutes or more. If a page
is finally loaded, scrolling through it is o.k. Ican also enter a complete url,
but once I press Enter I have to wait.... Browsing with firefox does not have
this speed issues, so it has nothing to do with my internet connection speed.
If I check the task manager is is the browser process which takes up full cpu
power.

   * What led up to the situation?
After upgrade from stretch to buster everything works fine but chromium is
extremly slow even though it looks like it is the same chromium package (I was
using testing for the chromium browser before).

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
After recommendation from reportbug I updated to latest unstable package, but
the issue remains. I also disabled hardware acceleration in settings and
chrome://flags. This didn't help either.

   * What was the outcome of this action?
The issue is still there.

   * What outcome did you expect instead?
Normal startup.




-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common      76.0.3809.62-1
ii  libasound2           1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0          2.30.0-2
ii  libatomic1           8.3.0-6
ii  libatspi2.0-0        2.30.0-7
ii  libavcodec58         7:4.1.3-1
ii  libavformat58        7:4.1.3-1
ii  libavutil56          7:4.1.3-1
ii  libc6                2.28-10
ii  libcairo-gobject2    1.16.0-4
ii  libcairo2            1.16.0-4
ii  libcups2             2.2.10-6
ii  libdbus-1-3          1.12.16-1
ii  libdrm2              2.4.97-1
ii  libevent-2.1-6       2.1.8-stable-4
ii  libexpat1            2.2.6-2
ii  libflac8             1.3.2-3
ii  libfontconfig1       2.13.1-2
ii  libfreetype6         2.9.1-3
ii  libgcc1              1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0         2.58.3-2
ii  libgtk-3-0           3.24.5-1
ii  libharfbuzz0b        2.3.1-1
ii  libicu63             63.1-6
ii  libjpeg62-turbo      1:1.5.2-2+b1
ii  libjsoncpp1          1.7.4-3
ii  liblcms2-2           2.9-3
ii  libminizip1          1.1-8+b1
ii  libnspr4             2:4.21-1
ii  libnss3              2:3.45-1
ii  libopenjp2-7         2.3.0-2
ii  libopus0             1.3-1
ii  libpango-1.0-0       1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpci3              1:3.5.2-1
ii  libpng16-16          1.6.36-6
ii  libpulse0            12.2-4
ii  libre2-5             20190101+dfsg-2
ii  libsnappy1v5         1.1.7-1
ii  libstdc++6           8.3.0-6
ii  libvpx5              1.7.0-3
ii  libwebp6             0.6.1-2
ii  libwebpdemux2        0.6.1-2
ii  libwebpmux3          0.6.1-2
ii  libx11-6             2:1.6.7-1
ii  libx11-xcb1          2:1.6.7-1
ii  libxcb1              1.13.1-2
ii  libxcomposite1       1:0.4.4-2
ii  libxcursor1          1:1.1.15-2
ii  libxdamage1          1:1.1.4-3+b3
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.4+dfsg1-7+b3
ii  libxrandr2           2:1.5.1-1
ii  libxrender1          1:0.9.10-1
ii  libxslt1.1           1.1.32-2
ii  libxss1              1:1.2.3-1
ii  libxtst6             2:1.2.3-1
ii  zlib1g               1:1.2.11.dfsg-1

Versions of packages chromium recommends:
pn  chromium-sandbox  <none>

Versions of packages chromium suggests:
pn  chromium-driver  <none>
ii  chromium-l10n    76.0.3809.62-1
pn  chromium-shell   <none>

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
pn  chromium-sandbox                        <none>
ii  fonts-liberation                        1:1.07.4-9
ii  libgl1-mesa-dri                         18.3.6-2
pn  libu2f-udev                             <none>
ii  notification-daemon                     3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.14.5.1-1
ii  upower                                  0.99.10-1

-- Configuration Files:
/etc/chromium.d/README changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, Jul 20, 2019 at 3:15 PM Tobias Rupf wrote:
> Sorry for the report I found the issue - is is the extension "Passman". I 
> couldn't remove it easily due to the slow browser action but than I just 
> deleted the user profile and the issue was gone. Installing the extensions 
> one by led me to the above mentioned one.

--- End Message ---

Reply via email to