New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 726651 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

free_list.h:118 Memory corruption detected on recent kernel

Reported by yanyan.r...@gmail.com, May 26 2017

Issue description

Chrome Version       : 58.0.3029.110 (Developer Build) (64-bit)
OS Version: Linux 4.11.2-1-ARCH #1 SMP PREEMPT Mon May 22 06:53:49 CEST 2017
URLs (if applicable) : http://news.google.com
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x: OK
     IE 7/8/9:

What steps will reproduce the problem?
1. chromium --disable-seccomp-sandbox --single-process http://news.google.com
2.
3.

What is the expected result?
Crash instanly

What happens instead of that?
terminal message:
Gtk-Message: Failed to load module "pk-gtk-module"
[21375:21400:0526/173909.855889:ERROR:proxy_service_factory.cc(116)] Cannot use V8 Proxy resolver in single process mode.
[21375:21400:0526/173909.926120:ERROR:proxy_service_factory.cc(116)] Cannot use V8 Proxy resolver in single process mode.
../../third_party/tcmalloc/chromium/src/free_list.h:118] Memory corruption detected. 
Received signal 11 SEGV_MAPERR 000000000039
#0 0x55eb527d7f06 <unknown>
#1 0x55eb527d82b9 <unknown>
#2 0x7f633acbafe0 <unknown>
#3 0x55eb50e16660 <unknown>
#4 0x55eb50e19f62 <unknown>
#5 0x55eb56eeaf4a <unknown>
#6 0x55eb528661d9 operator new[]()
#7 0x55eb52dd140e <unknown>
#8 0x55eb52dd146e <unknown>
#9 0x55eb52dd2c47 <unknown>
#10 0x55eb52dcfe3f <unknown>
#11 0x55eb52dc5d5a <unknown>
#12 0x55eb52d8b57d <unknown>
#13 0x55eb52d8fa33 <unknown>
#14 0x55eb561b1a45 <unknown>
#15 0x55eb52d8fa33 <unknown>
#16 0x55eb52fde8da <unknown>
#17 0x55eb52d90709 <unknown>
#18 0x55eb53421268 <unknown>
#19 0x55eb534201bb <unknown>
#20 0x55eb53421c6b <unknown>
#21 0x55eb53421f4c <unknown>
#22 0x55eb534217db <unknown>
#23 0x55eb53424fbe <unknown>
#24 0x55eb53423e0f <unknown>
#25 0x55eb534244f3 <unknown>
#26 0x55eb53424639 <unknown>
#27 0x55eb53455664 <unknown>
#28 0x55eb55d493c2 <unknown>
#29 0x55eb55d49598 <unknown>
#30 0x55eb55d495db <unknown>
#31 0x55eb5283c5b8 <unknown>
#32 0x55eb528385fd <unknown>
#33 0x7f633acb02e7 start_thread
#34 0x7f6332a1854f __GI___clone
  r8: 0000000000000000  r9: 00007f6332a60360 r10: 632079726f6d654d r11: 0000000000000000
 r12: 0000000000000001 r13: 0000000000000000 r14: 000055eb56ef1300 r15: 00003a866f4d3050
  di: 0000000000000000  si: 00007f62fd50f440  bp: 0000000000000056  bx: 00007f62fd50f430
  dx: 0000000000000056  ax: 0000000000000056  cx: 00007f633acb9f1d  sp: 00007f62fd50f418
  ip: 000055eb50e16660 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000039
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Please provide any additional information below. Attach a screenshot if
possible.



 
Components: Internals>Core
Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue using chrome stable version 61.0.3163.100 on Ubuntu 14.04. Tried by following the steps mentioned in the description.

@ yanyan.ryan.leung: Request you to please update chrome to the latest stable available and retry again. Please update us with your observations.

Thanks.!
Status: WontFix (was: Unconfirmed)
Closing issue as Wontfix due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Thanks..!

Sign in to add a comment