New issue
Advanced search Search tips

Issue 766159 link

Starred by 4 users
Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
ajha@chromium.org
dtapu...@chromium.org
Components:
EstimatedDays: ----
NextAction: 2017-10-03
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Memory increases enormously during run of ffmpeg.js (built by Emscripten) in a worker.

Reported by fredj...@gmail.com, Sep 18 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. npm install ffmpeg.js
2. Convert a webm stream as described in https://www.npmjs.com/package/ffmpeg.js#via-web-worker
(this describes how to invoke a worker, though to do transcoding the code needs to be modified)
3. See the memory used by Chrome increase during transcoding.

What is the expected behavior?
Transcoding without incremental increase of memory used.

What went wrong?
At about 2GB of memory usage, I get the "Aw, snap!" error message.

Did this work before? N/A 

Chrome version: 60.0.3112.113  Channel: n/a
OS Version: OS X 10.12.6
Flash Version: 

As can be seen from the screen shot, it is not javascript memory that is increasing.
Screen Shot 2017-09-15 at 12.16.33.png
786 KB View Download

Comment 1 by dtapu...@chromium.org, Sep 18 2017

Components: -Blink Blink>JavaScript
How large of a webm stream are you converting? I'm guessing this is a standard OOM message you are getting because the example ffmpeg.js code isn't streaming at all so you require memory for the input stream and output stream before it ends up getting written out.

Do you have a URI for reproduction including the webm files?
Have you looked at a heap profile? See https://developers.google.com/web/tools/chrome-devtools/memory-problems/heap-snapshots

Comment 2 by dtapu...@chromium.org, Sep 18 2017

Labels: Needs-Feedback
NextAction: 2017-10-03

Comment 3 by fredj...@gmail.com, Sep 20 2017 

It is a webm file of 134MB, and here is the code to reproduce it https://github.com/fredrikj/transcode-chrome-crash

(The readme mentions that you need to download the media file from an S3 bucket)
When I open the page, the page will crash when transcoding is almost done.

I attach a screen shot of a memory profile I attempted to take just before the crash. As far as I can see, there is nothing particular about it. It display "JS Heap" less than 7.4 MB which seems really small.
Screen Shot 2017-09-20 at 07.47.15.png
591 KB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 20 2017

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by monor...@bugs.chromium.org, Oct 3 2017 

The NextAction date has arrived: 2017-10-03

Comment 6 by hablich@chromium.org, Oct 4 2017

Components: -Blink>JavaScript Blink>MemoryAllocator
JavaScript memory looks low. rerouting.

Comment 7 by ajha@chromium.org, Oct 5 2017

Cc: ajha@chromium.org
Labels: Needs-Milestone Needs-Feedback
fredjoha@: Could you please attach the crash id from chrome://crashes as well, for further investigation.

Somehow I am unable to install npm on Windows,Mac and Linux as this requires Admin access on my corp laptop to install and run npm install http-server -g.

Comment 8 by ellyjo...@chromium.org, Feb 12 2018

Status: WontFix (was: Unconfirmed)
Mac triage: closing old issue without feedback or repro.
►

Sign in to add a comment