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