[opensuse-factory] Chromium crashes after update to version 55
Hi anybody, after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form. The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem. Has anybody recognized a similar behavior? Is this a known bug? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Rene', 2016-12-16 14:48 GMT+01:00 René Krell <renda.krell@gmail.com>:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
I had the problem a couple of days ago while trying to book hotels. I tried a couple of times before switching to Chrome (55.0.2840.100)
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
I've done a quick search and google doesn't show anything Fra
René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16.12.2016 14:48, René Krell wrote:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
I have the same, yes. I always use chrome when I'm editing forms :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys, Could you please try packages from network:chromium? Followed up by chromium-beta and chromium-dev? Also having backtrace and open bug would be really helpful. Thanks Tom
2016-12-16 15:43 GMT+01:00 Tomas Chvatal <tchvatal@suse.cz>:
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys,
Could you please try packages from network:chromium?
Followed up by chromium-beta and chromium-dev?
Also having backtrace and open bug would be really helpful.
Thanks
Tom
Regarding the backtrace: At the moment I can see just this at the console each time: *** stack smashing detected ***: /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-s wap terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7f93e8eef14b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f93e8f76aa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f93e8f76a70] /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-swap(+0x389e4f6)[0x55fbeb39c4f6] BTW: The crash is easily reproducible - I'm just sending a mail at the GMail web site to myself. Approximately a second after pressing the Send button Chromium crashes. And I'm sure it will crash also after sending this one, but at least it sends it before going down. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Dec 16, 2016 at 04:32:46PM +0100, René Krell wrote:
2016-12-16 15:43 GMT+01:00 Tomas Chvatal <tchvatal@suse.cz>:
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys,
Could you please try packages from network:chromium?
Followed up by chromium-beta and chromium-dev?
Also having backtrace and open bug would be really helpful.
Thanks
Tom
Regarding the backtrace: At the moment I can see just this at the console each time:
*** stack smashing detected ***: /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-s wap terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7f93e8eef14b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f93e8f76aa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f93e8f76a70] /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-swap(+0x389e4f6)[0x55fbeb39c4f6]
BTW: The crash is easily reproducible - I'm just sending a mail at the GMail web site to myself. Approximately a second after pressing the Send button Chromium crashes. And I'm sure it will crash also after sending this one, but at least it sends it before going down.
can you run in gdb and see if that gives some form of backtrace? There is a buffer overflow happening, which should not be the case. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-12-16 16:35 GMT+01:00 Marcus Meissner <meissner@suse.de>:
On Fri, Dec 16, 2016 at 04:32:46PM +0100, René Krell wrote:
2016-12-16 15:43 GMT+01:00 Tomas Chvatal <tchvatal@suse.cz>:
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys,
Could you please try packages from network:chromium?
Followed up by chromium-beta and chromium-dev?
Also having backtrace and open bug would be really helpful.
Thanks
Tom
Regarding the backtrace: At the moment I can see just this at the console each time:
*** stack smashing detected ***: /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-s wap terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7f93e8eef14b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f93e8f76aa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f93e8f76a70] /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-swap(+0x389e4f6)[0x55fbeb39c4f6]
BTW: The crash is easily reproducible - I'm just sending a mail at the GMail web site to myself. Approximately a second after pressing the Send button Chromium crashes. And I'm sure it will crash also after sending this one, but at least it sends it before going down.
can you run in gdb and see if that gives some form of backtrace?
There is a buffer overflow happening, which should not be the case.
Ciao, Marcus
The backtrace from gdb doesn't show more, I don't know where to find the debugsymbols package. Chromium goes down apparently after: Thread 15 "BrowserBlocking" received signal SIGABRT, Aborted. A shortened transcript follows: rkrell@rkrell:~> gdb /usr/lib64/chromium/chromium GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 ... uninteresting output Reading symbols from /usr/lib64/chromium/chromium...(no debugging symbols found)...done. (gdb) run Starting program: /usr/lib64/chromium/chromium Missing separate debuginfos, use: zypper install chromium-debuginfo-55.0.2883.75-2.1.x86_64 ... uninteresting things happen .... [New Thread 0x7fffc1f5f700 (LWP 17665)] *** stack smashing detected ***: /usr/lib64/chromium/chromium terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7fffece0614b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7fffece8daa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7fffece8da70] /usr/lib64/chromium/chromium(+0x389e4f6)[0x555558df24f6] ======= Memory map: ======== 370711b92000-370711b93000 ---p 00000000 00:00 0 ... the huge memory map isn't probably interesting 7ffffffdd000-7ffffffff000 rw-p 00000000 00:00 0 [stack] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Thread 15 "BrowserBlocking" received signal SIGABRT, Aborted. [Switching to Thread 0x7fffd59c6700 (LWP 16847)] 0x00007fffecdc85af in raise () from /lib64/libc.so.6 René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Got to add one important output I faded out: A Parser-blocking, cross-origin script, http://rs.martinus.sk/delivery/spc.php?zones=..., is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross-origin script, http://rs.martinus.sk/delivery/spc.php?zones=..., is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details. A Parser-blocking, cross-origin script, https://rs.martinus.sk/delivery/fl.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/571854794679 9104 for more details. Right after this, when creating the next "thread", the crash happens: [New Thread 0x7fffc1f5f700 (LWP 17665)] *** stack smashing detected ***: /usr/lib64/chromium/chromium terminated -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Marcus Meissner píše v Pá 16. 12. 2016 v 16:35 +0100:
On Fri, Dec 16, 2016 at 04:32:46PM +0100, René Krell wrote:
2016-12-16 15:43 GMT+01:00 Tomas Chvatal <tchvatal@suse.cz>:
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys,
Could you please try packages from network:chromium?
Followed up by chromium-beta and chromium-dev?
Also having backtrace and open bug would be really helpful.
Thanks
Tom
Regarding the backtrace: At the moment I can see just this at the console each time:
*** stack smashing detected ***: /usr/lib64/chromium/chromium --ppapi-flash- path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-s wap terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7f93e8eef14b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f93e8f76aa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f93e8f76a70] /usr/lib64/chromium/chromium --ppapi-flash- path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-swap(+0x389e4f6)[0x55fbeb39c4f6]
BTW: The crash is easily reproducible - I'm just sending a mail at the GMail web site to myself. Approximately a second after pressing the Send button Chromium crashes. And I'm sure it will crash also after sending this one, but at least it sends it before going down.
can you run in gdb and see if that gives some form of backtrace?
There is a buffer overflow happening, which should not be the case.
Ciao, Marcus
Managed to get meaningful trace, but I won't be able to followup before christmas I suppose: #0 0x00007fffecdc85af in raise () from /lib64/libc.so.6 #1 0x00007fffecdc99aa in abort () from /lib64/libc.so.6 #2 0x00007fffece06150 in __libc_message () from /lib64/libc.so.6 #3 0x00007fffece8da77 in __fortify_fail () from /lib64/libc.so.6 #4 0x00007fffece8da40 in __stack_chk_fail () from /lib64/libc.so.6 #5 0x0000555558df27a6 in autofill::CreditCard::ConvertMonth(std::__cxx11::basic_string<unsigned short, base::string16_char_traits, std::allocator<unsigned short> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int*) [clone .part.114] () HTH Tom -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdm4bBIAGRMvy+dWx5KJGjI7uO+gFAlhaUhAACgkQ5KJGjI7u O+hiARAArjFq8Q/Fh48rIWQjgUaLuSXABlmgjeyH9QUtP8f8ADZOYiNmJImyz5AP NE8CipucSa2YPux/4Ad1CHmc7EOdYigoEuXjc1iEpP5IagJj0xX14oUfhRhKjFPg RbVpwEd/1CKTR6wuMo+pYPa013ke7fGzxGaQPsP+sKQr71xkHeNiYUgzzpGr5ywn n7AvMmBe59Ezm+cBcA85UP1KF/4iemgUURG99kU9Q/uG/x7V1Hy4AsEx/K+XYuql +uCH/2SUC/zORHH+49YOYhZ2q2PD1RFVFOJ8gpB8OqZ9BXI1SNXhQWVjqUJIAVka BJwJadSBI/pBcmlfag0/IvHvELbUMe+es++ySt3QsRo6IssJplnzXkqBqS1qE7dR 2fFHKqLIJsZ3xuNbYJf84oyoKRDioAXEByPgik5eH/0A1+Tt0u1qvg8GFjN6LAxp jmU7m/wE3zFRj1Y7yzrAweDWGykMrC1QGLxJ6D+6NNWhtoiv3zE+uwFcCsw+/zO4 nARt4HfK8Q4YGdu9WJnj591Oe89wPDHlLN3z9FjqhAyuuV6tfyiPwxY7wszohKlg davkIQQF9AQ5xissCzdFjPKEDpFkSdkYtUmsnyuTAnsA6DTyUZL0Vk/jyGeT2kBg 0KiZ+KzRVIdClPFraBN0oc6hOCIrJYAeuh6kx4sfACjAzzmof1g= =q8oK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Dec 21, 2016 at 6:57 AM, Tomas Chvatal <tchvatal@suse.cz> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Marcus Meissner píše v Pá 16. 12. 2016 v 16:35 +0100:
On Fri, Dec 16, 2016 at 04:32:46PM +0100, René Krell wrote:
2016-12-16 15:43 GMT+01:00 Tomas Chvatal <tchvatal@suse.cz>:
René Krell píše v Pá 16. 12. 2016 v 14:48 +0100:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
René
Hello guys,
Could you please try packages from network:chromium?
Followed up by chromium-beta and chromium-dev?
Also having backtrace and open bug would be really helpful.
Thanks
Tom
Regarding the backtrace: At the moment I can see just this at the console each time:
*** stack smashing detected ***: /usr/lib64/chromium/chromium --ppapi-flash- path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-s wap terminated ======= Backtrace: ========= /lib64/libc.so.6(+0x7214b)[0x7f93e8eef14b] /lib64/libc.so.6(__fortify_fail+0x37)[0x7f93e8f76aa7] /lib64/libc.so.6(__fortify_fail+0x0)[0x7f93e8f76a70] /usr/lib64/chromium/chromium --ppapi-flash- path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.186 --password-store=detect --enable-threaded-compositing --ui-disable-partial-swap(+0x389e4f6)[0x55fbeb39c4f6]
BTW: The crash is easily reproducible - I'm just sending a mail at the GMail web site to myself. Approximately a second after pressing the Send button Chromium crashes. And I'm sure it will crash also after sending this one, but at least it sends it before going down.
can you run in gdb and see if that gives some form of backtrace?
There is a buffer overflow happening, which should not be the case.
Ciao, Marcus
Managed to get meaningful trace, but I won't be able to followup before christmas I suppose:
#0 0x00007fffecdc85af in raise () from /lib64/libc.so.6 #1 0x00007fffecdc99aa in abort () from /lib64/libc.so.6 #2 0x00007fffece06150 in __libc_message () from /lib64/libc.so.6 #3 0x00007fffece8da77 in __fortify_fail () from /lib64/libc.so.6 #4 0x00007fffece8da40 in __stack_chk_fail () from /lib64/libc.so.6 #5 0x0000555558df27a6 in autofill::CreditCard::ConvertMonth(std::__cxx11::basic_string<unsigned short, base::string16_char_traits, std::allocator<unsigned short> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int*) [clone .part.114] ()
So..there is an stack overflow here that is stopped before any harm is done.. hrmmm. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On 16 Dec 14:48, René Krell wrote:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
Can you try to install http://download.opensuse.org/repositories/home:/namtrac:/branches:/network:/... and see if it fixes the problem for you? Thanks, ismail -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
2016-12-17 9:31 GMT+01:00 İsmail Dönmez <idoenmez@suse.de>:
Hi,
On 16 Dec 14:48, René Krell wrote:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The native Chrome 55.0.2883.87 (64-bit) doesn't come with this problem.
Has anybody recognized a similar behavior? Is this a known bug?
Can you try to install http://download.opensuse.org/repositories/home:/namtrac:/branches:/network:/... and see if it fixes the problem for you?
Thanks, ismail
@Ismail: I'm now at TW 20161216 and tried the build you suggested - it is still crashing in forms, mostly when pressing the Submit button. Not really fixed here. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-12-16 14:48 GMT+01:00 René Krell <renda.krell@gmail.com>:
Hi anybody,
after the recent update of the chromium package to version 55 the Chromium (64-bit) browser is frequently crashing, and only when editing some input fields or pressing a button in a form.
The problem hasn't happened again for me since the update to chromium-55.0.2883.87-1.1 along with all the updates in TW 20161222 - just to close this discussion. René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Cristian Rodríguez -
Francesco Montesano -
İsmail Dönmez -
Marcus Meissner -
René Krell -
Stephan Kulow -
Tomas Chvatal