New issue
Advanced search Search tips

Issue 871737 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Bug in web page case memory leak - when chrome fill RAM the PC freezes

Reported by jiri.kub...@gmail.com, Aug 7

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. We have a web page tied to MQTT broker. This web page cause currently undiscovered memory leak.
2. The chrome consumes all available system RAM 
3. System freezes and only HW reboot solve this problem

What is the expected behavior?
Not allow the opened tab consume all available memory.

What went wrong?
We have a web page with three.js 3D library. In this web page is some kind of bug which cause memory leak. The main problem is that it is possible to see in Task manager - performance window how the memory is rapidly consumed how ever in system processes is visible that the chrome maintain constant amount of ram. When I reload web page then Task manager - performance window is visible the memory usage drop. 

The two scenario happen 
1) when I leave it to consume as much memory as it want then it stops around 10.3GB (cca 6.5GB is caused by this issue, total RAM is 11881MB). Ten something happen and it didnt allow consume more. Lets say it this is correct.

2) When I postpone it a bit for example system sleep or somehow delay the browser than it probably cache some events and flush them out at once. In this case it consume all available RAM which cause full or partial system hangup and is it not possible to control the OS (ie mouse not moving, not possible to close/open anything). In this case the Chrome should not allow this situation happen. 

Did this work before? N/A 

Chrome version: 68.0.3440.84  Channel: stable
OS Version: 7
Flash Version: NA

The bug in out webpage will be fixed, it wolud ba a trivial bug. But the trivial bug in web page might not cause system failure. However I believe that it could be used as system killer - you open the web page and then system is dead - who knows what else could happen...
 
Labels: Needs-Triage-M68
Cc: susan.boorgula@chromium.org
Labels: Needs-Feedback Triaged-ET
jiri.kubias@ Thanks for the issue.

Request you to provide the URL of the web page where this issue can be reproduced, which will help in further triaging.

Thanks..
Hi,
the web page is not public. I can provide you some example via PM. I have discovered that slowly filling thrre.js (javascript 3D library) with objects can fill up the memory. We can reach max RAM (12GB) in 150sec - then widnows system totally hangup. When the filling is too quickly then Chrome recognizes the probable RAM overflow and stops the page. So there is some protection, but when the filling is relatively slow then the protection didnt catch it.

Regards, 
Jiri 

Sign in to add a comment