Updates:
Status: Assigned
Owner: [email protected]
Labels: video
Comment #1 on issue 18278 by [email protected]: Chrome on Linux goes
invisible and chews CPU and RAM after a day
http://code.google.com/p/chromium/issues/detail?id=18278
Hey Dan,
Thanks for the report. I basically just rewrote the whole alsa
implementation, including changing the
threading model and wait state. The code is out for review, so I don't
think there's much need to examine
more of the exact state of chrome.
If you could maybe grab a few more snapshots of the alsa status (maybe 5
samples in a quick loop?), just to
see how much the avail number changes, that'd be nice.
I'm thinking the basic problem is that we've run out of audio data, and the
audio output stream keeps saying
"I have more space! Give me more!" I'll look into trying to reproduce, and
put in throttling code on monday.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
