Core generated by chrome process occasionally
Reported by
xmh...@gmail.com,
Oct 27 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: Don't have the exactly reproduce steps, we're using chrome driver to do some automation tests on Chrome. What is the expected behavior? There should be no core files. What went wrong? We found some core files generated by Chrome process. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". BFD: /opt/google/chrome/libwidevinecdm.so: version count (454) does not match symbol count (453) Core was generated by `/opt/google/chrome/chrome --type=renderer --enable-logging --log-level=0 --no-s'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f9ae262ac37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f9ae262ac37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f9ae262e028 in __GI_abort () at abort.c:89 #2 0x00007f9aeb1331d2 in ?? () #3 0x0000000000000000 in ?? () Did this work before? N/A Chrome version: Google Chrome 60.0.3112.101 Channel: stable OS Version: Ubuntu 14.04.5 LTS Flash Version: Shockwave Flash 27.0 r0 I cannot understand the message core, was it caused by "BFD: /opt/google/chrome/libwidevinecdm.so: version count (454) does not match symbol count (453)"?
,
Nov 1 2017
xmhubj@ Can you please provide us the detailed steps and screen cast of the same when you are seeing this issue which will be helpful for further triaging. Thanks..
,
Nov 3 2017
As it was generated occasionally, also chrome was run(XVFB) and controlled by program via chromedriver, it is a little bit hard to provide detailed steps. All I have is the core files, is there anyway to upload cores? In the meanwhile, will try my best to get information see if I can reproduce this issue steadily.
,
Nov 3 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 7 2017
The issue seems to be out of TE-scope as it is related to chrome driver and performing automation tests. Hence, adding the label TE-NeedsTriageHelp for further investigation from dev team
,
Dec 29 2017
looks like this issue is related to issue https://github.com/SeleniumHQ/docker-selenium/issues/87 chromedriver occasionally hangs and then selenium ChromeDriver force to clean chromedriver process, thus google chrome processes are aborted, core dumped.
,
Dec 29 2017
I think it's good to close this issue. Thanks guys anyway.
,
Feb 10 2018
Closing as per #7 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xmh...@gmail.com
, Oct 30 2017