New issue
Advanced search Search tips

Issue 607092 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Massive processes got mmap fail due to the process leakage of Chrome

Reported by richard....@htc.com, Apr 27 2016

Issue description

Steps to reproduce the problem:
Run monkey test

What is the expected behavior?

What went wrong?
Massive processes got mmap fail due to Out of kernel VM limitation (392MB) in single device.
By logs, there were hundreds process com.android.chrome:sandboxed_process exist while issue happen.
And hundreds process com.android.chrome:sandboxed_process got signal 11 earlier but no tombstone dump.

// process com.android.chrome:sandboxed_process got signal 11 immediately while it just started
04-19 01:49:21.369   971  1000 I ActivityManager: Start proc 11171:com.android.chrome:sandboxed_process18/u0i77 for service com.android.chrome/org.chromium.content.app.SandboxedProcessService18
…
04-19 01:49:21.979 11171 11189 I cr_LibraryLoader: Time to load native libraries: 347 ms (timestamps 9888-235)
04-19 01:49:21.979 11171 11189 I cr_LibraryLoader: Expected native library version number "49.0.2623.105", actual native library version number "49.0.2623.105"
04-19 01:49:21.989 11171 11189 I chromium: [INFO:library_loader_hooks.cc(144)] Chromium logging enabled: level = 0, default verbosity = 0
04-19 01:49:22.109   467   467 I Zygote  : Process 11171 exited due to signal (11)

// hundreds sandboxed_process got signal 11.
04-18 23:40:40.834   467   467 I Zygote  : Process 13628 exited due to signal (11)
04-18 23:43:19.404   467   467 I Zygote  : Process 14148 exited due to signal (11)
04-18 23:45:08.664   467   467 I Zygote  : Process 14660 exited due to signal (11)
04-18 23:38:01.254   467   467 I Zygote  : Process 13006 exited due to signal (11)
04-19 01:49:22.109   467   467 I Zygote  : Process 11171 exited due to signal (11)
04-19 01:52:00.649   467   467 I Zygote  : Process 11695 exited due to signal (11)
04-19 01:19:07.813   467   467 I Zygote  : Process 25546 exited due to signal (11)
04-19 01:08:50.593   467   467 I Zygote  : Process 22261 exited due to signal (11)
…
04-20 00:35:24.410   467   467 I Zygote  : Process 27273 exited due to signal (11)
04-20 00:29:20.630   467   467 I Zygote  : Process 25828 exited due to signal (11)
04-20 00:29:46.570   467   467 I Zygote  : Process 26076 exited due to signal (11)
04-20 00:32:44.220   467   467 I Zygote  : Process 26643 exited due to signal (11)
04-20 00:23:27.270   467   467 I Zygote  : Process 21769 exited due to signal (11)
04-20 00:14:17.730   467   467 I Zygote  : Process 19550 exited due to signal (11)
04-20 00:18:10.310   467   467 I Zygote  : Process 20594 exited due to signal (11)
04-20 00:20:49.760   467   467 I Zygote  : Process 21248 exited due to signal (11)
04-20 01:13:15.383   467   467 I Zygote  : Process 13625 exited due to signal (11)
04-20 14:57:59.623   467   467 I Zygote  : Process 19059 exited due to signal (11)
04-20 14:45:50.543   467   467 I Zygote  : Process 15245 exited due to signal (11)

// Total 392MB and used by com.android.chrome:sandboxed_process more than 200MB due to process leakage
@kernel log
<6>[129392.331295] c2    311 [K] vmalloc : 0xe6800000 - 0xff000000   ( 392 MB)
<6>[129392.331343] c2    311 [K] vmalloc used : 392634368 bytes
<6>[129392.331381] c2    311 [K] end of dump vmallocinfo

// There are 118 com.android.chrome:sandboxed_process, each will use 2MB binder share memory
<6>[129615.104088] c0    116 lowmemorykiller: [ pid ]   uid  total_vm      rss cpu oom_score_adj  name
…
<6>[129615.110243] c0    116 lowmemorykiller: [ 5977] 99059    219131     2401   2   0 Chrome_ChildIOT <- com.android.chrome:sandboxed_process0
<6>[129615.110321] c0    116 lowmemorykiller: [15141] 99060    212181     2401   2   0 Chrome_ChildIOT <- com.android.chrome:sandboxed_process1
<6>[129615.110406] c0    116 lowmemorykiller: [15357] 99061    219146     2401   2   0 Chrome_ChildIOT <- com.android.chrome:sandboxed_process2
<6>[129615.110478] c0    116 lowmemorykiller: [15583] 99062    212172     2401   2   0 CrRendererMain  <- com.android.chrome:sandboxed_process3
<6>[129615.110550] c0    116 lowmemorykiller: [15817] 99063    219146     2401   2   0 Chrome_ChildIOT <- com.android.chrome:sandboxed_process4
<6>[129615.110629] c0    116 lowmemorykiller: [ 3317] 99064    212174     2401   2   0 Chrome_ChildIOT
<6>[129615.110709] c0    116 lowmemorykiller: [ 4545] 99065    212172     2401   2   0 Chrome_ChildIOT
<6>[129615.110832] c0    116 lowmemorykiller: [ 6023] 99066    212174     2401   2   0 Chrome_ChildIOT
<6>[129615.110942] c0    116 lowmemorykiller: [ 6531] 99067    212179     2401   2   0 Chrome_ChildIOT
<6>[129615.111105] c0    116 lowmemorykiller: [13036] 99068    212202     2401   2   0 Chrome_ChildIOT
<6>[129615.111203] c0    116 lowmemorykiller: [13659] 99069    212459     2401   2   0 Chrome_ChildIOT
<6>[129615.111282] c0    116 lowmemorykiller: [14170] 99070    212466     2401   2   0 Chrome_ChildIOT
<6>[129615.111353] c0    116 lowmemorykiller: [14683] 99071    213322     2401   2   0 Chrome_ChildIOT
<6>[129615.111431] c0    116 lowmemorykiller: [22282] 99072    212198     2403   2   0 Chrome_ChildIOT
<6>[129615.111504] c0    116 lowmemorykiller: [22521] 99073    213320     2403   2   0 Chrome_ChildIOT
<6>[129615.111579] c0    116 lowmemorykiller: [22720] 99074    219176     2403   2   0 Chrome_ChildIOT
<6>[129615.111660] c0    116 lowmemorykiller: [22956] 99075    218926     2403   2   0 Chrome_ChildIOT
<6>[129615.111735] c0    116 lowmemorykiller: [25565] 99076    212199     2403   2   0 CrRendererMain
<6>[129615.111813] c0    116 lowmemorykiller: [11192] 99077    212216     2402   2   0 Chrome_ChildIOT <- com.android.chrome:sandboxed_process18
<6>[129615.111885] c0    116 lowmemorykiller: [11714] 99078    213333     2402   2   0 Chrome_ChildIOT
<6>[129615.111961] c0    116 lowmemorykiller: [19695] 99079    212319     2420   2   0 Chrome_ChildIOT
<6>[129615.112034] c0    116 lowmemorykiller: [19749] 99080    213441     2420   2  58 Chrome_ChildIOT
<6>[129615.112117] c0    116 lowmemorykiller: [19793] 99081    213441     2420   2  58 Chrome_ChildIOT
<6>[129615.112195] c0    116 lowmemorykiller: [19811] 99082    219169     2421   2  58 Chrome_ChildIOT
<6>[129615.112300] c0    116 lowmemorykiller: [19822] 99083    213441     2420   2  58 Chrome_ChildIOT
<6>[129615.112393] c0    116 lowmemorykiller: [19838] 99084    219269     2420   2   0 Chrome_ChildIOT
<6>[129615.112472] c0    116 lowmemorykiller: [19917] 99086    213442     2420   2  58 Chrome_ChildIOT
<6>[129615.112545] c0    116 lowmemorykiller: [19924] 99085    213448     2420   2  58 Chrome_ChildIOT
<6>[129615.112624] c0    116 lowmemorykiller: [19946] 99089    219291     2420   2  58 Chrome_ChildIOT
<6>[129615.112700] c0    116 lowmemorykiller: [19954] 99088    219292     2420   2  58 Chrome_ChildIOT
<6>[129615.112778] c0    116 lowmemorykiller: [19956] 99090    219553     2420   2   0 Chrome_ChildIOT
<6>[129615.112858] c0    116 lowmemorykiller: [19957] 99087    217566     2420   2  58 Chrome_ChildIOT
...

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 50.0.2661.89  Channel: stable
OS Version: M60
Flash Version: NA
 
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 27 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment