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