stacktrace on chromium initialization
Reported by
t...@jujit.su,
Jun 18 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: 1. open chromium 2. bang! What is the expected behavior? What went wrong? λ chromium Received signal 7 BUS_ADRERR 7f6efffa5000 #0 0x561f7020b7c6 <unknown> #1 0x561f7020bc3d <unknown> #2 0x7f6f18818940 <unknown> #3 0x561f7023ec47 <unknown> #4 0x561f7023f230 <unknown> #5 0x561f7023d43d <unknown> #6 0x561f7016aaa3 <unknown> #7 0x561f7016ab59 <unknown> #8 0x561f700e2afa <unknown> #9 0x561f700e3819 <unknown> #10 0x561f700e47bc <unknown> #11 0x561f6ec8eeaa <unknown> #12 0x561f6efdf60a <unknown> #13 0x561f6ec8cfcb <unknown> #14 0x561f6ec92166 <unknown> #15 0x561f6ec8adb2 <unknown> #16 0x561f6fe4af9f <unknown> #17 0x561f71217b4a <unknown> #18 0x561f6fe499f4 <unknown> #19 0x561f6e726184 ChromeMain #20 0x7f6f1019643a __libc_start_main #21 0x561f6e72603a _start r8: 0000000000000000 r9: 00000000935ddd43 r10: 0000000000000000 r11: 0000000000000246 r12: 000000000000000e r13: 00000000935ddd43 r14: 0000000000800000 r15: 0000000000000000 di: 0000000000000000 si: 0000000000000000 bp: 00007f6efffa5000 bx: 000005fcc29841c0 dx: 00007f6efffa5000 ax: 0000000000000000 cx: 0000000000000000 sp: 00007ffd23a87700 ip: 0000561f7023ec47 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000007 trp: 000000000000000e msk: 0000000000000000 cr2: 00007f6efffa5000 [end of stack trace] Calling _exit(1). Core file will not be generated. Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 59.0.3071.86 Channel: n/a OS Version: arch Flash Version: Shockwave Flash 22.0 r0 not sure what the cause is. ASLR probably makes this trace useless, but maybe the register content in _start is interesting.
,
Jun 19 2017
Unable to reproduce the issue with chromium build 59.0.3071.104 (Latest Stable) available and also using chrome stable version 59.0.3071.104 on Ubuntu 14.04 t@jujit.su: Request you to please use chrome and give a try, please help us with a crash ID generated if reproduced on chrome. This will help us to triage the issue better. Thanks.!
,
Nov 7 2017
We are unable to reproduce the issue in latest chrome stable build #62.0.3202.89. Marking it as WontFix since there are no feedback from user more than a month.Feel free to raise a new issue if still facing. Thank You! |
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Jun 19 2017