[Pkg-chromium-maint] Bug#823186: chromium: crashes on many websites

Boris Pek tehnick at debian.org
Tue May 3 09:48:55 UTC 2016


control: reopen 823186 =
control: notfixed 823186 50.0.2661.75-2
control: severity 823186 important


Hi,

>>  Chromium become completely unusable at many websites since version
>>  50.0.2661.75-1. See screenshot and stack trace examples in attachments.
>>  And this is not duplicate of bug #821154, because watching videos at
>>  youtube.com have been fixed in 50.0.2661.75-2 and still works, but other
>>  websites -- do not.
>>
>>  After updating from chromium 49.0.2623.108-1 some packages are no longer
>>  required:
>>     libavcodec-ffmpeg56 (7:2.8.6-1+b2)
>>     libavformat-ffmpeg56 (7:2.8.6-1+b2)
>>     libavutil-ffmpeg54 (7:2.8.6-1+b2)
>>     libswresample-ffmpeg1 (7:2.8.6-1+b2)
>>
>>  Probably chromium was built incorrectly it lacks some mandatory features.
>
> This issue was fixed in 50.0.2661.75-2.

Please read bug reports carefully before closing them.

In 50.0.2661.75-2 you have fixed only HTML5 videos on websites like youtube.com.

But problem from this bug report is not fixed nor in 50.0.2661.75-2, nor in
50.0.2661.94-1. It 100% reproducible. For example, open URL [1] and chromium tab
will crash immediately. Another crash you may see if you click on any play
button at [2]. And there are more affected websites. In my case the most
annoying problem is that I can't access to my email correspondence via Web UI,
as you may see at screenshot in attachments.

I have tested chromium with and without extensions.

[1] https://www.chess.com/echess/game?id=131722832
[2] https://music.yandex.ru/artist/233138


Next:

$ apt-cache show chromium
Package: chromium
...
Version: 50.0.2661.94-1
...
Architecture: i386
...
Depends: libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4),
 libavcodec57 (>= 7:3.0) | libavcodec-extra57 (>= 7:3.0),
 libavformat57 (>= 7:3.0), libavutil55 (>= 7:3.0), libc6 (>= 2.15),
 libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14),
 libexpat1 (>= 2.0.1), libfontconfig1 (>= 2.11), libfreetype6 (>= 2.4.2),
 libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.41.1),
 libgnome-keyring0 (>= 3.2.2-2~), libgtk2.0-0 (>= 2.24.0),
 libjpeg62-turbo (>= 1.3.1), libnspr4 (>= 2:4.9-2~) | libnspr4-0d (>= 1.8.0.10),
 libnss3 (>= 2:3.13.4-2~) | libnss3-1d (>= 3.12.4), libpango-1.0-0 (>= 1.14.0),
 libpangocairo-1.0-0 (>= 1.14.0), libpci3 (>= 1:3.3.1-1),
 libspeechd2 (>= 0.7.1), libstdc++6 (>= 5.2), libx11-6 (>= 2:1.4.99.1),
 libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1),
 libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxml2 (>= 2.7.4),
 libxrandr2 (>= 2:1.2.99.2), libxrender1, libxslt1.1 (>= 1.1.25), libxss1,
 libxtst6, x11-utils, xdg-utils
...

I don't see anything related to libswresample. It may be related to the problem
or not related. Just a note which may be useful.


My system is up to date Debian Sid with i686-pae kernel.

Please ask if you need more info or any tests, but do not just close bug report.

Best regards,
Boris



More information about the Pkg-chromium-maint mailing list