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

Issue 664474 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Google Chrome is crashes because unable utilize all virtual memory

Reported by mikhail....@gmail.com, Nov 11 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2914.3 Safari/537.36

Steps to reproduce the problem:
1. Open a lot of tab and windows
2. 
3. 

What is the expected behavior?

What went wrong?
Crash messages

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: 56.0.2914.3  Channel: dev
OS Version: Fedora 25
Flash Version: Shockwave Flash 24.0 r0

[mikhail@localhost service]$ free -h
              total        used        free      shared  buff/cache   available
Mem:            30G         29G        331M        288M        896M        280M
Swap:           59G         28G         30G

[mikhail@localhost service]$ vmstat -s
     31856384 K total memory
     30648852 K used memory
     28289192 K active memory
      1852500 K inactive memory
       267768 K free memory
         1064 K buffer memory
       938700 K swap cache
     62494716 K total swap
     29780732 K used swap
     32713984 K free swap
      3467692 non-nice user cpu ticks
         6358 nice user cpu ticks
       518288 system cpu ticks
      3583170 idle cpu ticks
       999025 IO-wait cpu ticks
        32685 IRQ cpu ticks
        39769 softirq cpu ticks
            0 stolen cpu ticks
    259911372 pages paged in
    198200921 pages paged out
     55723572 pages swapped in
     45959455 pages swapped out
    127027160 interrupts
    398487609 CPU context switches
   1478853584 boot time
        61725 forks

As you can see memory consumption stopped at 29Gb physical memory and 28Gb memory in swap partition. Computer have 30G swap memory is unallocated, but Google Chrome begin crashes.

May be this is Linux kernel bug. Anyway it must be fixed.
 
Скриншот 11.11.2016 16-59-35-863.png
43.0 KB View Download
Labels: M-56
Screenshot from 2016-11-19 21-43-51.png
198 KB View Download
Screenshot from 2016-11-19 21-43-55.png
499 KB View Download
day later
Screenshot from 2016-11-20 21-38-05.png
266 KB View Download
Screenshot from 2016-11-20 21-38-10.png
499 KB View Download
Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Tested the same on Linux 14.04 chrome version 56.0.2924.3 with more tabs and windows (around 15 windows with multiple tabs) - did not observe any tab crash

Please find the screenshot

Could you please upgrade to latest dev and let us know if issue still exists
Screenshot from 2016-11-28 17:12:31.png
132 KB View Download
issue still exists in 56.0.2924.3 dev (64-bit)
Crash dump id:   bf29d10f00000000 
which occurred when Chrome allocated magical 29Gb in swap.

$ uname  -r
4.8.10-300.fc25.x86_64
Screenshot from 2016-11-29 00-15-37.png
370 KB View Download
I see that on your screen is not enough open tabs.

For reproduction:
1. Get powerfull computer with 32Gb RAM
2. Make swap partition 64Gb RAM
3. Open as many tabs to take the whole virtual memory. (swap must be used 63Gb before we see first crash, but we see first crash at 29Gb)
Yet another crash ID: b41ec92300000000
Screenshot from 2016-11-29 13-49-33.png
352 KB View Download
system log
system.log
543 KB View Download
Today updated to Version 56.0.2924.10 dev (64-bit)

And have new batch of crashes

Crash dump id:   0cf2c48f00000000
Crash dump id:   9150648f00000000
Crash dump id:   e3d6572300000000

Screenshot from 2016-11-30 18-58-58.png
235 KB View Download
Crash dump id:   995b985f00000000
Crash dump id:   92efbc8f00000000
Screenshot from 2016-12-01 01-37-00.png
311 KB View Download
Crash dump id: 1a06025f00000000
Screenshot from 2016-12-01 07-56-55.png
390 KB View Download
Mergedinto: 629429
Status: Duplicate (was: Unconfirmed)
Based on the similar stack trace merging the issue 629429
Hey, in this bug report we talk not about crashed. We talk about memory utilization by Google Chrome. I see that Chrome got out of memory problem, but system have available memory.

And I can't see discussion in 629429.
I am still create duplicate report because can't know that happens in 629429.

Sign in to add a comment