New issue
Advanced search Search tips

Issue 862546 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

FaceDetector memory leak

Reported by coloured...@gmail.com, Jul 11

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Use FaceDetector.detect
2. See memory leak upon GPU process

What is the expected behavior?
There is no memory leak

What went wrong?
Takes all available memory on device, then crashes with OOM 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 10
Flash Version: 

I'm able to provide additional help with testing and debugging
 
temp.html
868 bytes View Download
Tested on Stable, tested on Canary, tested on Chrome and Chromium. Behaves same way.

Labels: Needs-Triage-M67
Labels: Needs-Feedback Triaged-ET
Tested the issue on chrome reported version# 67.0.3396.99 using Windows-10 with steps mentioned below:
1) Launched chrome reported version, dragged and dropped the file provided in comment# 0 and clicked on "Allow" for permission
2) Opened Devtools > Console, seen error "Uncaught ReferenceError: FaceDetector is not defined at detectFace" and error value keep on increases
3) Opened Devtools > Performance, recorded the task and clicked on stop, observed the GPU field, seen GPU timing

@Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, if possible could you please provide screencast of the issue which help in better understanding and further triaging it.

Thanks!
862546.mp4
4.5 MB View Download
Ah yes, please turn on experimental web features flag in chrome://flags


2018-07-18_20-46-18.png
53.6 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 18

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
As per comment# 4, tested the issue by enabling the experimental web features from chrome://flags, but seen same behaviour as mentioned in comment# 3 and didn't faced chrome crashes issue.

@Reporter: could you please provide chrome crash id by navigating to chrome://crashes which helps us in further triaging it.

Thanks!
Components: Internals>GPU
Status: WontFix (was: Unconfirmed)
As there isn't any Feedback from reporter since long time, closing this issue and marking it as Won't Fix.

@Reporter: Requesting you to file/raise a new issue if this happens in latest chrome versions.

Thanks!

Sign in to add a comment