New issue
Advanced search Search tips

Issue 755663 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Potential memory leak in TtsDispatcher::OnSetVoiceList

Project Member Reported by etienneb@chromium.org, Aug 15 2017

Issue description

Traces were provided by mad@, which is running chrome canary with native heap profiling.

Chrome Canary M62, Windows 10

The attached stackframes are showing
  * 120K strings allocated in "TtsDispatcher::OnSetVoiceList" (~4 Meg)
  * 40K blink::WebSpeechSynthesisVoice::WebSpeechSynthesisVoice (~1.6 Meg)

This is leaking about 5.6 Meg in the browser process.
 
bug1.png
32.0 KB View Download
Labels: Performance-Memory
bug2.png
33.4 KB View Download
We don't know if it's related, but the renderer process was using 900M.
taskmanager.png
8.5 KB View Download
Labels: -Pri-3 Needs-Investigation Pri-2
Status: Available (was: Untriaged)
Erik - we should start thinking about allocating folks to dig into these sorts of bugs.

Comment 7 by etienneb@google.com, Aug 28 2017

We are for most of these bugs.
The most common answer is to get a repro.
When it's hard to repro, we are spending some time to try to make a case.

But, if you know the right people to assign them... feel free. :)
Project Member

Comment 8 by sheriffbot@chromium.org, Aug 28

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Sign in to add a comment